The first of four (1 of 4) Solution Implementation Boards conveys the progress of each Feature as it progresses from it initial addition to the Solution Backlog to becoming "Ready" for implementation.
This part has yet to be migrated. Expect an updated version in the next few months.
Analysis & Design: Feature Planning
Recall that a Feature corresponds to some type of Business Value within a given Epic. Basically, a Feature defines some want that the business has for this Solution. In some cases, there may be just a few Features which relate to an Epic. In other cases, there may be dozens. Regardless, in either case, all Features share the same lifecycle.
It is one thing to say 'I want...'Â It is quite another to define that want into something actionable.
ensure everyone on the same page
ensure it fits within the bigger picture
capture testable requirements
This is not the time to worry about how to provide what the business wants. That is left to the Stories which relate to, and enable, their parent Feature.
For instance, someone in the business may say 'I want
Implementation Task 1 of 4: Feature Planning described the steps through which each Feature progresses as part of Analysis & Design. In that Part, each Step
Making Features "Ready"
The Feature Planning Board contains five (5) columns. Each column offers insights as to where things are in the 'bigger picture'.
Columns Progress Left to Right
Before delving into the specifics of each column, there are several general statement to make. Firstly, each Feature begins in the left-most column. In the steps to make it "Ready", it will progress to the right, through each column until it reaches the right-most column. In general, a Feature's movement from left to right indicates is progression through the Feature Planning Task.
Each column conveys information about a Feature which distinguishes each Feature from all others. in short, anyone can locate a Feature on the board and gain a pretty good understanding of where that Feature stands in the grand scheme of things. That is, if they understand how to read the Feature Planning Board.
Columns Prioritize Top to Bottom
All Features within a column share many of the same characteristics. That is, each is in a similar state in its overall lifecycle. One characteristic they do not share is their priority. For that, one must look to where the Feature ranks within each column.
Columns segment Features by progress, and stack them based on priority. In general, the higher the priority the Feature, the higher in the column the Feature should sit. The highest priority Feature in any column should appear at the top of the column. Likewise, the lowest priority Feature should appear at the bottom of the column.
Of course, priorities change over time. What is a high-priority change one day, is not the next. How to boards convey this?
To fast-track a Feature, it should appear
No two Features have the same priority. This is apparent because there are no two Features side-by-side in any column. That one Feature appears above another within a column indicates that is has the higher priory. Generally, this is known a forced-ranking. And it ensures there is no confusion about 'what's next'?
Solution Owners regularly look to the Features in the Backlog and make adjustments based on the latest information available. Generally, this should occur at least weekly.
A Features rank, or position, in the
What Each Column Across the Board Conveys
Refer to IT1: Feature Planning for more information about making Features "Ready" for inclusion into a Release.
Column 1 of 5 - Backlog (Open)
Where everything starts. Any new Feature, Story, or Bug begins its life in the Solution Backlog. The backlog is simple the pile of work which the initiative has yet to do.
Every change which anyone would like to see begins in the Backlog. However, it is important to recognize that just because a Feature exists in the Backlog does not mean that the change it represents will ever occur. Indeed, prioritizing desired changes is one of the result of the Feature Planning task.
Column 2 of 5 - On Roadmap (To Do)
to migrate
Column 3 of 5 - In Analysis (In Analysis)
TBD
Column 2 of 5 - In Review (In Review)
TBD
Colun 2 of 5 - "Ready" (Ready)
TBD