Thought for the Day

I've come across several ideas recently that need addressing. One is from Ron Jeffries blog 

If you are not producing working, running, tested usable software in every single Sprint or iteration, you are not [yet] “doing” Agile, you are not [yet] “doing” Scrum.

While there is nothing in this statement to object to, it's one of those statements that is necessary but not sufficient.

I say this because of an engagement in Agile Transformation for a tier-one Aerospace and Defense client, who's moving from their stage-gate product development process to agile.

If we're Doing Agile, it means

• We are producing testable outcomes every sprint
• The term usable needs to be defined.
  • Usable to whom?
    • The testing process?
    • The end User?
    • The downstream processes? Cyber, Performance assessment, UI/UX validation, and verification? 
• What functionality and Capabilities are available every Sprint?
  •  It may well be we need 4 Sprints to produce the Feature needed by the customer
    •  In a DO-178 Flight Safety domain, it requires external V&V to confirm working is working In Accordance With (IAW)
  • So working needs to have attached to it working for whom.

These generalizations of the agile thought leaders need to be put into practice in the domain and context

• Building the updated warehouse app for the rubber shoe company?
• Building a Joint Precision Autonomous Landing System for the US Navy? 

Both are done with Scrum

Just a Thought