Fail-Fast | Glossary

Definition

‘Fail-Fast’ is an oft-debated, controversial topic that involves trying something new, obtaining rapid feedback and quickly inspecting and adapting. It’s practiced in methods of high uncertainties , where it’s less expensive to start a product. The task is to learn whether the decisions work. If they don’t, the Project is killed fast, and focus is  moved on to the next thing.

It’s seen as a controversial move in the general press and media, which often sees it as reckless and irresponsible. It’s also a much criticized move in Agile/Lean/DevOps where the ‘fail often’ approach is not encouraged.

Further Reading

  • “Fail Fast, Fail Often: How Losing Can Help You Win”(book), by Ryan Babineaux

 

Vision | Glossary

Definition

Every Scrum Project needs a vision. One that is clear and well-defined. It’s important for people to understand the exact nature of the release, and not just vaguely understand and process it to a less than optimal capacity. The vision acts as the project’s true ‘guiding light’, and becomes a benchmark towards which the team works towards.

It is the overlooking goal that everyone in the team must share. The Product Owner, Scrum Master, Development Team, Stakeholders and the eventual customers are all part of the overall vision. The Product Owner is overall responsible for the ‘vision’ of the project and guiding it towards success, with close collaboration with the members of the team.

Further Reading

  •  “Scrum : the art of doing twice the work in half the time” (book), by Jeff Sutherland.