Re: [scrumdevelopment] Re: projects board
The status division in the PDF you sent is how can I say, you have a
waterfall view of your projects.
Since you are trying to do Agile, let me give you something more specific.
Example, follow your projects by goals.
Break each project in bigger goals, than you break those bigger goals
in shorter ones. Make those short goals fixed in timeboxes. Let's say,
two weeks. If you do this, you will have expected iterations and
releases for your projects.
And here is the magic... :-)
One project can be waiting for something to start. After it starts, it
can be on development (where you can follow those goals) or you have
that project blocked by some reason (you have an impediment to solve).
After completion, the project can be closed or the project can be
canceled for some reason. So you have green status, yellow and red
status. Yellow can be an impediment that is not blocking you but is
something to take care ASAP. Red is a real road block, that needs
You have some statuses available for customer review and also team
review. If you do that, they will become phases in your cycle. Don't
do that. Follow one project using your goals and work to bring your
customers closer to your teams to review those goals.
This way they will be following their projects closer. Ask the team to
tell the team how they are doing daily and after the end of one
timebox, review your goal versus what was delivered by the team and
check how you can improve with your team.
You need something simple. Scrum can really help you. You need a heartbeat.
Ask to your directors what they want to know about projects. What kind
of metrics they want to measure. Remember that the team will behave
based on this.
If a project is blocked, I would like to understand why. If a project
misses its goal, I want to know before that happens. If a project goes
live, I want to measure ROI, I want to understand how much money I'm
giving back to my customer. So, those may be good variables to follow.
On Mon, Dec 8, 2008 at 1:35 PM, Johanna Rothman <jr@...> wrote:
> Ron is giving good advice, so listen to him :-) In addition, consider
> what you're trying to do, which is manage the project portfolio.
> You've got a picture of the low-level view of the project portfolio,
> from the pictures you attached. In addition, I find a high level view
> very helpful. That's the month-by-month or iteration-by-iteration view
> of all of the projects.
> In addition, hopefully not everyone is working on *all* projects. If
> they are not, you can group projects in a number of ways:
> - who's working on them
> - who the projects are for
> - whatever else floats your boat.
> The key when you put the big picture together is to look at the
> highest ranking projects. Make sure those are fully staffed, and that
> the teams are making progress. Since you are not yet using an agile
> process, if you can move to an incremental lifecycle, where you finish
> features in totality before moving on to the next one, you can see
> progress on a periodic basis.
> For pictures that might make sense to you, look at:
> I wonder if people are actually on all of the projects. If so, I bet
> not full time.
> On Dec 8, 2008, at 7:47 AM, Flávio Steffens de Castro wrote:
>> Hi Ron,
>> the problem is that everyone works in every project. So, people are
>> always asking for "who is the responsable for project A?", "what is
>> the release date of project B?" and "what is the next milestone/date
>> of project C?".
>> We dont have a scrum/agile process here. I have to say that we are
>> in the beggining. The meaning of the board is to try to create the
>> VISUAL concept of agile. People here still have some things like
>> "Oh, that will never work here". I already have the same problem in
>> my other work, but there was more simple.
>> The project is one of the first step to show how a taskboard is
>> important... how making the information visible is important.
>> One thing that may "populate" the board is that we have a lot of
>> "update/maintance projects"... and maybe some of them doesnt need to
>> be visible.
>> Also, Im using card + magnetic stuff to fix the projects (cards) in
>> the board. And Im seeing that its hard to manage them.
>> Im attaching the plan of the board. You can see that Im using in the
>> board: columns as status, cards as projects, and post-its in the
>> card to milestones and dates.
>> Flavio Steffens de Castro
>> On Mon, Dec 8, 2008 at 10:01 AM, Ron Jeffries <ronjeffries@...>
>> Hello, Flávio. On Monday, December 8, 2008, at 5:00:25 AM, you
>> > the idea is to make visible to all the company the status of the
>> > The information that everyone wants to know is: what are the
>> milestones and
>> > release dates?
>> I'd like to challenge that idea. Why in the world does "all the
>> company" need to know the status of 60 different projects?
>> > Daniel said a thing that is right: im looking for a project board,
>> not a
>> > taskboard. Also, the board will be a point where the managers can
>> make daily
>> > meetings to discuss/plan the following day.
>> You have managers who are interested in and meet about all sixty of
>> your projects and make decisions about all sixty of them every day?
>> > Anyway, Im gonna check for your suggestions :)
>> :) Thanks. Seems to me that if this must be done, it ought to be
>> awfully simple.
>> Ron Jeffries
>> To follow the path:
>> Look to the master; Follow the master; Walk with the master;
>> See through the master; Become the master. -- Modern Zen Poem
> Rothman Consulting Group, Inc. 781-641-4046
> Speaker, Author, Consultant - Managing Product Development
> http://www.ayeconference.com, Nov 8-12, 2009
> To Post a message, send it to: scrumdevelopment@...
> To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...! Groups Links