Contact

Resources

Program Board

The Program Board is generated during PI Planning and is used by the teams to visualise delivery and coordinate collaborations during a PI. This article looks at the Program Board's use during PI Execution.

Image of game board built using Team Space

Serious gaming to encourage and nurture an agile mindset, beyond just software and product delivery teams, using jargon-light agility cards.

The Program Board is generated during PI Planning and is used by the teams to visualise delivery and coordinate collaborations during a PI. This article looks at the Program Board's use during PI Planning.

Fulfilling the Vision of Stefan Bengtsson - Chalmers as a World Leader

Portfolios should set Work-In-Process limits on what they do to ensure that the organisation focuses on getting things done. This post looks at factors that influence how those Work-In-Process limts should be set and explores how it's not a simple numeric limit.

The Program Board is generated during PI Planning and is used by the teams to visualise delivery and coordinate collaborations during a PI. This article looks at the Program Board's setup and structure.

Activity Spaces provide one powerful description of the Common Ground of Essence. Although useful just by name, there is a detailed description of each Activity Space in the Essence Standard. This article lists them in a slightly easier to find way.

A collection of Essence Activity Space Cards

The Activity Spaces are an often-overlooked aspect of Essence. These 15 descriptions of types of common activities that all software development teams will do are often overshadowed by the specific activities from Practices. But as this article shows they have value in their own right and can be a powerful tool to help teams improve.

Welcome to the amalgamation of a short series of articles on crafting effective, well-formed objectives as part of the SAFe® Program Increment (PI) / Big Room Planning activity. We have seen a lot of confusion surrounding the use of PI objectives; confusion that often results in: Resistance to their use and; The production of poorly formed team objectives that appear to be completely redundant as they just list the Features being addressed. The first step to creating well-formed, useful objectives is for everyone to understand why they are so important. Covered in this document: Why do we need PI Objectives when we have Features? Writing good PI Objectives PI Objectives and the PI Planning Process PI Objectives Beyond PI Planning: Reaffirming and Monitoring Your Commitments  

Card showing th4e checklists for Stakeholder 'Recognized' state

Arguably, the most important aspect of any development endeavor is the Stakeholders - the people for whom we are creating the solution. Yet, how often do you see teams focus more on the product than its users, sometimes with dreadful consequences. Luckily, making sure your Stakeholders are being managed well needn't be hard. The Essence kernel includes a specific alpha for Stakeholders, with the states they can be in and checklists to help you.

Contact Us