Agile Development

Many of the creators of Essence are also members of Agnostic Agile. Thus the need for Essence and its structure, elements and properties is based on the same values/needs shared with the founders and other members of Agnostic Agile.

One of the main goals for LV= GI has been the need to accelerate the pace of getting their products to market. It was essential for them to get in front of opportunities, be proactive and stay ahead of the curve. To survive in a hugely competitive marketplace, they must also keep moving in the right direction to remain a front runner.

With more and more people working from home, many organisations that have adopted SAFe® are having to adapt their processes in order to accommodate completely dispersed teams.

With more and more people working from home, many organisations that have adopted SAFe® are having to adapt their processes in order to accommodate completely dispersed teams.

With more and more people working from home, many organisations that have adopted SAFe® are having to adapt their processes in order to accommodate completely dispersed teams.

Key Takeaways Use Case 2.0 expand on the ideas embodied in user stories Some up-front design is needed in all software development projects For any product you need the skeleton system that has the key requirements embodied in it early on Any system should be able to be represented by between 10 and 20 key use cases

This instructional guide provides a brief introduction to the Alphas and presents seven different games that can be played with the Alpha State Cards by software development teams.

In this first of a new series of blog articles, author Roly Stimson discusses how Use-Case slices are a simple but powerful technique to identify and prioritize small increments of releasable value and how these can be split (if and when needed) into smaller items that you can independently prioritize, schedule, build, test and demonstrate.

A short series of articles on crafting effective, well-formed objectives as part of the SAFe® Program Increment (PI) / Big Room Planning activity. A series of four related articles: 1. Why do we need PI Objectives when we have Features? 2. Writing good PI Objectives 3. PI Objectives and the PI Planning Process 4. PI Objectives Beyond PI Planning: Reaffirming and Monitoring Your Commitments

In the second of this Use Cases in Practice series of blog articles, author Roly Stimson discusses how a use case model provides a simple, big, visible picture that provides critical value context, which represents a powerful tool that can be used as part of Scrum sprint reviews to ensure that the team and the stakeholders reflect meaningfully on what has been achieved in the context of the overall solution goals and value, and adjust future work objectives, priorities and plans accordingly.