Blog

Scaled Agile Gold Partner

Visualisation Technique for Constructing & Understanding SAFe Program Backlogs

I was recently asked to help facilitate and to act as coach at a multi-day kick-off event for a new Agile Release Train (ART). The agenda initially looked a lot like that of the SAFe Program Increment (PI) Planning event, but there were immediate differences, the main one being a restricted attendee list due to ongoing team recruitment. The people in the room consisted largely of the SAFe Program level: Release Train Engineer (RTE), Product Management, Product Owner, Architecture, and a few Subject Matter Experts...
Product Ownership Health Check

Successful Traits for Effective Product Ownership

Key to realizing benefits from agile is strong customer representation through empowered Product Ownership – to guide the team in delivering a solution that maximizes end-user value. But this is also often the hardest agile practice to get working effectively, because of its novelty for many stepping into the role, and because of the challenges in balancing time commitments with existing business responsibilities, and combining incisive decision-making with broad-based stakeholder representation and negotiation. Download the infographic and post it on your wall as a daily reminder of what's needed or better yet, download our Product Ownership Health Check Guide.
Agile Team work

We must work as a team! Teamwork is critical! There’s no ‘I’ in team!

We must work as a team! Teamwork is critical! There’s no ‘I’ in team! These mantras are plentiful and many Agilists believe that success at the team level is the foundation to success at the organizational level. But what does it really mean to work as team and is there a common recipe to build and grow a successful agile team? Agile believes in principles before practices and in multi-disciplined, self-organizing teams. All teams need direction and guidance, but with an agile approach no one should be telling the team how to do their job. Teams need to be empowered to make choices rather than be told exactly what to do. But sometimes things can start to unravel and too much time and energy can be wasted arguing about the basics. You can forget about scaling agile if your team is unable to clearly demonstrate the value of agile at the team level. But, get the basics right at the team level and engaged, highly motivated, cross-functional teams of teams can follow.