LACE (CCSQ Lean Agile Center of Excellence)

Page tree

Versions Compared

Old Version 21

changes.mady.by.user Marc Santini

Saved on

compared with

New Version Current

changes.mady.by.user Marc Santini

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. The value is clear and understood (Why?)
  2. The desired outcome is clear (What?)
  3. The user/persona/beneficiary is defined and is the recipient of the value delivered (Who?)
  4. Binary acceptance criteria are present
  5. Relevant guidance, information, and documentation links are included
  6. Potential risks, blockers, unknowns, and dependencies​ are notednoted 
  7. Defect issues contain enough information to investigateDefects are clearly defined with:
  8. Steps to reproduce​
  9. Expected results​
  10. Screenshots/logs​
    11. Test data



Reference for Feature

The Feature can be clearly described.The feature is well enough understood that its extent and purpose can be clearly explained by the Product Management / Product Ownership Team
Small enough to fit within a PIThe estimates for the Feature indicate that it is small enough to be easily completed within a standard Program Increment (PI).
The Feature is testableThe need for any unusual or novel testing is clear and factored into the estimates
The Feature is feasibleFor Business Features the architectural and technical risks are under control and it is expected that the Feature can be implemented without any significant technical issues. For experimental enablers and spikes the constraints are understood and the financial exposure is in-line with the probability of success.
The potential benefits are understoodThe Feature has a well understood, measurable benefits hypothesis.
The Feature has a clear ownerIt is clear who the team pulling the Feature should converse, and negotiate with, over the scope and extent of the Feature, and who will accept the Feature as done.
The level of key stakeholder involvement is understood.The details of any important external Stakeholders are known and the mechanisms to involve them in a timely way have been put in place.
The cost of delay is clearThe relative business / user value, time criticality, risk reduction and opportunity enablement are well enough understood that the Features cost of delay is clear. See the SAFe approach to Weighted Shortest Job First for more details.
Any ‘fixed’ requirements are knownAny specific, fixed, non-negotiable aspects of the Feature are known and their details are available. For example the specific actuarial calculations to be used in an insurance system.

...