Contact

Blog

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.

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.

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.

Essence Alphas Cards

Essence is one of the most exciting innovations in software engineering today - but what exactly is it? Unsurprisingly for something so powerful, with so many different use cases, Essence is often hard to explain. There are lots of articles describing the details, but in this article, we distil Essence down to a single page.

Picture of the Holy Grail

Our industry loves a fad - and in particular, we love to discover the Next Big Thing in development approaches. Each time we are promised a new (or improved) framework or playbook that will solve all our problems, and that we should immediately roll out to all our teams. And each time, we end up disappointed, without the results promised or anticipated, needing to look for a new Next Big Thing to repeat the cycle. It doesn't have to be that way, and the alternative needn't be as scary as it may seem. And it isn't another big framework!

Image of the Scrum Practice Sprint Review card. Pulled from the Scrum Essentials Practice developed in conjunction with Scrum Inc.

Scrum and its hybrids are the dominant approaches used by Agile teams today. However, despite Scrum being a seemingly simple framework, many teams struggle to apply Scrum well and fail to achieve the faster delivery of higher value products that are promised. Playing the Practice Spotlight game is a simple way to improve any team's understanding and application of Scrum.

The Scaled Agile Framework's recommended approach for prioritisation within the Portfolio is to use Weighted Shortest Job First (WSJF), but there are some challenges when trying to run WSJF at the Portfolio level. This series of posts explores those challenges, with this post focusing on what happens when Total Epic Effort is used within WSJF.

Contact Us