Very good culture
Debate, decide, do
Software Development * Project Management
A person who is good at the execution will know the importance of creating work breakdown structure (WBS).
A good executor makes things happen, or get things done (GTD). A good executor not just come up idea and plans, but know "how to" make thing happen. They know what the WBS looks like.
Coming up a WBS, from PMI's PMBOK perspective, is a planning task. It is a function performed by a project manager.
However, I found that coming up a work breakdown structure is actually sometime a technical job that requires people to have certain level of the domain knowledge. Similar projects have similar WBS, especially at the high level.structure. When I go further down to the detail level, I found that the work breakdown structure will be more specific and requires people to have the knowledge to come up the breakdown and come up the list of tasks.
A project manager is really a role the assigned resource plays. A project manager is really not a separate function. I feel that we cannot easily make a good project manager who can manage construction project well to be a project manager for software development. There are shared knowledge that can be useful for any project manager. The project manager to manage a specific type of project need to know that work down to certain level to do the project manager job.
Who should create the WBS? Can the job of creating WBS to be assigned to someone else?
I think that it cannot be totally avoid anyway when we go down to the detail levels. For a new project that has not yet been done before and no similar project the project manager can use to come up the WBS, the project manager need to work with the architect who need to come up the high level components to help project manager to manage the project.
I think that this process also define how the architect works with the development manager. I think that typically the person with the development manager title in software development organization should play the project manager role. Sometimes, a project leader or an architect may also play the project manager role. A person who never played the project manager can still be a good architect, but is never qualified to be a development manager.
1. Someday/Maybe List
This is a Wish List. If I have time I should spend some time on this task.
I still review it regularly to remind myself that I do not forget them.
This is different from the list that I will be regularly once a week on a specific scheduled time.
This is the list of tasks that I am not working on it. The items listed here are unplanned lists.
It could be a project that still has not yet been broken down.
It can be a project idea. They can be removed after researched and planned and the individual breakdown items ( not the whole item) are moved to other context category.
This a blog posting about Seven Problems with a Someday/Maybe List.
2. Special Occasions
I am assigning tasks to future of me under some occasions.
Typically these are part of my regular life. Either once a week or may be a particular time everyday.
The typical example used are @Home, @Work, @Errands, or Reading List.
I feel that it still very important to talk with people in person even we can send emails and using messaging. Having one on one with your boss and your directs are part of the system developed within my company.
My contexts are organized by people
@Weekly Staff Meeting
@Weekly IDC Meeting
@Home with kid
The more context you have, the more regular scheduled time blocks you have. It may become less flexible, but I feel that I will be more organized.
This is a good article that talks about GTD contexts - What is (not) a GTD context?