Success With Retrospectives
Summary Retrospectives are a fundamental practice in all agile frameworks. Retrospectives enable Agile delivery teams to continuously improve their performance […]
Summary Retrospectives are a fundamental practice in all agile frameworks. Retrospectives enable Agile delivery teams to continuously improve their performance […]
‘Big Room Planning’, or PI Planning, is one of the core events of the Scaled Agile Framework – SAFe. It’s
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
Scrum was introduced to address the unacceptably high failure rate of software projects. (The annually published CHAOS Report by the
“If you can’t explain it simply, you don’t understand it well enough”. Albert Einstein. Summary SAFe is an agile delivery
“Innovation is saying no to 1,000 things” – Steve Jobs Portfolio Management is the highest level planning process within an
The scaled agile framework (SAFe) enables organizations to transform business needs into working software in a consistent, repeatable way, using
“Plans are things that change” — Fujio Cho, Toyota “Plans are worthless, but planning is everything” — Dwight D. Eisenhower
Summary Additional governance is required to plan, and coordinate the execution of Program Increments. A dedicated role to support PI
“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
“We place the highest value on actual implementation and taking action. There are many things one doesn’t understand and therefore,