So, today I passed the LinkedIn assessment for the Agile methodologies, thumbs up. However, there are a few things I learned during the way that I want to take note of here.
In Scaled Agile Framework, if you just need to measure one thing, what is it?
Note: If you only want to measure one thing in the Scaled Agile Framework (SAFe®) or other frameworks, yes, it could be “cost of delay” (that is the official version, according to the SAFe® test). This is where I read.
Three key different things between task board and kanban board
What is the Enabler’s role in Scaled Agile Framework?
An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. Enablers are captured in the various backlogs and occur throughout the Framework. This is further reading.
What are the most common ways to split a story?
Further reading for story splitting is here:
- A practical guide to user story splitting for agile teams
- SPIDR – five simple techniques for a perfectly split user story
What Happens When A Story is Not Accepted by Product Owner?
Abandon it. In some cases, the story may be abandoned. This is a healthy response of a mature product owner, and it typically happens when the data does not provide the information the product owner was hoping to get. They see that what the team can realistically create based on what’s in the system is not what they or the stakeholders had envisioned.
That’s it so far.
Hope it helps sometimes you read this.