Uncategorized

About a year ago I wrote an article that presented Agile transformation as a fairly conventional iterative change program. Traditional

‘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

In Agile Data Science – Part 1 we reviewed some of the fundamental challenges of doing data science with agility,

“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,

“Mistakes are the portals of discovery.” – James Joyce, Ulysses   “Science, my lad, is made up of mistakes, but