Blog

In this short blog Ian Spence looks at how many Features a SAFe® Agile Release Train needs to prepare to be ready for their PI (Program Increment) / big room planning event.

IJI has been engaged with a major UK bank over the last 18 months helping them introduce new methods of working, and IBM’s Collaborative Lifecycle Management tooling to support these methods. Business Analysts now capture their requirements in Rational Requirements Composer (RRC), Solution Architects create their designs in Rational Software Architect (RSA) using the Unified Modelling Language (UML), Infrastructure & Security Architects add deployment topologies to the designs using RSA’s Deployment Planning extension, and everything is underpinned by Work Items and Source Control in Rational Team Concert (RTC).

The following blog provides a set of free, downloadable agile coaching cards that can be used by Agile Coaches, Scrum Masters and teams working in many different contexts. These cards have been developed while working outside of software and product development with government Defence teams and I’ve used these cards to teach agility and help develop an agile mind set.

The topic of “Can we have multiple Portfolios?” comes up fairly regularly in training courses, what are some of the implications and challenges associated with multiple Portfolios within ARTe.

The topic of “Can we have multiple Portfolios?” comes up fairly regularly in training courses, what are some of the implications and challenges associated with nested Portfolios within ARTe.

Scaled Agile Inc. have just announced SAFe 6.0, the latest version of the Scaled Agile Framework. The changes realign their core values and rephrase a key principle amongst many other tweaks and adjustments throughout the framework. Ivar Jacobson Intl. have updated the widely utilised SAFe® Principle cards to reflect the changes in SAFe 6.0.

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

Epics have a lifecycle, they don’t magically appear fully formed. There is work to be done to progressively elaborate a business case and if the Epic is approved then there is further work to progress the Epic through implementation. This post explores the Lifecycle of an Epic and the states it progresses through in that Lifecycle.

Epics, the Portfolio Level work artefact, flow through the Portfolio processes but the flow can be very slow. This post explores how the Epic Feedback loop provides rapid feedback for decision making about an Epic even if the Epic itself is long lived.