roadmap

WBS Out, Roadmap In

WBS Out, Roadmap In

If you are still using a Work Breakdown Structure (WBS), then you still have the waterfall mindset: task driven. Lean Agile mindset, however, is Value driven. Things of value are planned and delivered in Stories, not in tasks. Stories are chunked together in a meaningful Feature of value. Features are spread out into a quarterly (chunk of three months spread over a year length) roadmap. Stories spread out into two-week sprints. In Lean Agile, WBS is out... Roadmap is in! Product Managers...if someone is asking you to deliver a project plan in WBS format ... and you are in the…
Read More
On-track or Off-Track? Part II

On-track or Off-Track? Part II

One might ask the following: "Why bother checking? We "know" that we are on track already!" "Can we just keep working and deliver the work when we are done?" "Can we just tell you what tasks we did and have completed?" "May we provide you a PowerPoint deck, screenshots, metric, list of lessons learned from our Spikes, some documentation and toll gate decks?" Good questions! Think about those questions for a few minutes. The thing is, a few errors accumulated everyday/ every sprint/iteration... unchecked... for a whole program increment (PI) spells disaster. Does it make sense to show the incremental…
Read More
When does a Roadmap Become a Queue?

When does a Roadmap Become a Queue?

Good question: When does a roadmap become a queue? Backdrop: prioritized minimum marketable features (MMF) get pulled into Continuous Integration to Program Increment (PI) Planning. However, a PI can only hold so many features ... therefore, the unaccommodated features will have to be laid out over a series of succeeding PIs ... over a roadmap... A Sample Roadmapwhich can easily becomes a queue... which is not an ideal situation. Hence the good question: When does a roadmap become a queue? To be continued ...
Read More
Idea approved, now what’s next? Part IV

Idea approved, now what’s next? Part IV

Roadmap -- yes, you need a roadmap of the features. Do all the features fit in a program increment (PI)? Sometimes, features for a product span across two or more PIs ... depending on the prioritization, sequencing of the features (sequenced to hit a hard date/milestone, for example) and how large the Epic or Capability or Product that is going to be built. Usually, a PI is a quarter of a year long... 3 months long... 6 to 7 iterations (sprints)... 12 to 14 weeks long. Lay out the features over the roadmap (over a PI or series of PIs).…
Read More
X

Forgot Password?

Join Us