Scaled Agile Certification
Learning goals for Certified SAFe® Agilist
Lead the transformation to Business Agility with SAFe
Become a Lean-Agile Leader
Understand customer needs with Design Thinking
Enable Agile Product Delivery
Implement Lean Portfolio Management
Personally, I took this exam having participated on agile teams and been a part of scaled agile ARTs in the past. This experience helped greatly when studying for this certification.
Incremental VS Iterative
By Tim Brown
| May 5, 2020
|
Agile is just short-duration incremental development right? WRONG!
This is a KEY concept that people miss with Agile.
If someone can’t explain incremental vs iterative be scared! If you take the common Agile process at face value all you really have is an incremental approach that doesn’t differ much from waterfall methodologies. In every waterfall project I’ve ever worked on it involved breaking down the higher level requirements into pieces that could be built, tested, and delivered.
Agile Product Ownership in a Nutshell
By Tim Brown
| May 5, 2020
|
‘Suppose the stakeholders say “Can we get THESE features by christmas”. That’s a fixed time, fixed scope question. Looking at trend lines, Pat says “Nope, sorry, it ain’t gonna happen”, followed by “here’s how much we can get done by christmas” or “here’s how much more time we need”. It’s generally better to reduce scope than to extend time, because if we reduce scope first, we still have the option to extend the time later and add the rest of the stories.
MVP VS Earliest Testable/Usable/Lovable
By Tim Brown
| May 5, 2020
|
MVP is really the:
Earliest Feedbackable Product
Earliest Testable Product
Earliest Usable Product
Earliest Lovable Product
Making sense of MVP (Minimum Viable Product) – and why I prefer Earliest Testable/Usable/Lovable
Manifesto for Agile Software Development
By Tim Brown
| May 5, 2020
|
Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Principles behind the Agile Manifesto
By Tim Brown
| May 5, 2020
|
The 12 Principles behind the Agile Manifesto We follow these principles:
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project.