Delivery At Scale 2: Organizing for Scaled Delivery
Organizing for Scaled Delivery Summary Getting the right organizational structure in place is a critical prerequisite for successful scaling. Traditional […]
Organizing for Scaled Delivery Summary Getting the right organizational structure in place is a critical prerequisite for successful scaling. Traditional […]
Summary At scale, the definitions of the Product Goal and Product Backlog at scale are unchanged: the Product Goal serves
Summary Simple planning and execution governance is sufficient to coordinate, communicate and help keep teams and stakeholders informed and aligned.
The Improvement System Summary All improvement should be connected to business outcomes. Improvement frameworks can be leveraged to ensure alignment
On a daily basis, a Scrum Team understands its progress towards achieving the Sprint Goal, and, if necessary, adjusts its
One of the most important changes in how work gets done in an agile organization is the shift from doing
Summary KPIs are a way to measure the impact of development initiatives on business outcomes A way to measure the
What are the challenges in building a culture where everyone is engaged in continuous and sustained improvement? First, an organization’s
‘Big Room Planning’, or PI Planning, is one of the core events of the SAFe Scaled Agile Framework. It’s an
The Sprint Retrospective What: An opportunity for the Scrum Team to inspect itself and create a plan for improvements to
The Sprint Review What: Event held at the end of every Sprint to inspect the Increment and adapt the Product
The Daily Scrum The daily scrum (or stand-up) event is primarily for the development team. Others may attend but not
Sprint Planning What: Confirm what can be delivered in the upcoming sprint Identify the work needed to deliver the increment
Backlog Refinement What: Get User Stories ready: who/what/why acceptance criteria small enough to fit – split if necessary dependencies in
“Alan: Now, how to play the flute. (picking up a flute) Well, you blow in one end and move your fingers up
Massive amounts of data being generated and collected across virtually all parts of business ecosystems – manufacturing, supply chains, marketing,
In Agile Data Science – Part 1 we reviewed some of the fundamental challenges of doing data science with agility,
Consider parts 1-2 as Agile for Data Scientists. This addendum could be considered Data Science for Agilists, and seeks to illustrate
“Scrum exposes every inadequacy or dysfunction within an organization’s product and system development practices. The intention of scrum is to
Try this … Get proposed feature list Assign “business value points” using Fibonacci – just relative ranking – use Planning