This is the fourth on the series of posts about the AMR-One Project. Today I will talk about the Work Breakdown Structure tool as a way to get the tasks of a project.
The concept
Once we have somehow the scope, requirements, or definition of what we are going to do, we could prepare the Work Breakdown Structure (WBS).
The Project Management Institute (PMI) PMBOK defines the WBS as a “deliverable oriented hierarchical decomposition of the work to be executed by the project team.”
Basically is an iterative process that takes one large work product, and breaks it down into smaller, manageable work packages.
In a WBS such elements are the items that are estimated in terms of resource requirements, budget, and timing
WBS applied to AMR-One Project
In the case of AMR-One, I made a simplification of the process, aligning the Product Roadmap, the Requirements, and WBS.
So in the WBS I added all Initiatives from the Roadmap as L1, and the Features or Epics as L2. Also I added one column to define the version of the product where these Epics will apply.
WBS related to Roadmap and Requirements
I didn’t split it into more levels as in this way it is quite aligned with the requirements already defined.
Now from here, and having the architectural approach mentioned in the previous video, we could start identifying atomic tasks within each Epic. This is work to do with the technical team, identifying dependencies, resources, time, and cost estimation.
Epics decomposition in atomic activities
And that is all so far.
In the next post, I will explain to you how to prepare a good Project Plan. It is not only to have a plan of tasks, time, and costs. It is much more than that!
See the following video for more details:
No comments:
Post a Comment