A Day in the life of an Agile Ready User
8:30 am: After a few minutes checking emails, Shannon logs into Agile Ready and her Product Owner Dashboard displays the status of her three teams. SealTeam 7 and show GREEN. Last week she and her Business Systems Analyst team reviewed and edited, based on Product and Backlog Scoring both Sprint Backlogs and approved their readiness.
she sees that Product Backlog has gone RED below the Product Threshold. She doesn’t understand why. She will check later with Patel, her Business Systems Analyst helping her with .
11:00 am: Patel and Shannon, with laptops, each log into Agile Ready. After a few minutes of drilldown Patel remembers an email from Joe, another BSA, that he transferred 25 new user stories from the backlog to the backlog. These user stories were related to a new feature that the team developed that should be implemented in the legacy rewrite.
The stories are low rated and drop the backlog readiness threshold. Shannon and Patel schedule a 1 hour working session at 2 pm to work on these stories.
Shannon supports three agile teams; Girl-Band, SealTeam7 and .
and SealTeam7 are working on the same project, a legacy rewrite while is developing the MVP for a new product.
Her boss is Jamie, Product Manager for the entire company.
Late in the Day: Jamie, Shannon’s boss, walks into her office and sits for an impromptu meeting. Jamie tells her that she’ll be running the Project full-time and that Patel is going to become Product Owner for the Legacy Rewrite.
Two new teams are being added to the project and will need to start sprinting in three weeks. Jamie says a new mobile billing and payments module has to be part of the MVP and the spec is in her email.
Shannon says no problem. A prior mobile and billing implementation last year that was postponed is still available in Agile Ready and easily re-purposed to seed the initial set of backlogs.
While Jamie is in the room, she creates a new product line and connects the prior backlogs to the new product line.
“We can start backlog refinement next week. We’ll be ready before the teams are ready.”