Archive for the ‘story development’ Tag

Last Responsible Moment Thinking in Agile

Friday, March 25th, 2016

Last week, I travelled from UK through USA to Caribbean and back to UK. It was a week of long flights, not enough sleep and included mid week volunteering for MP for Richmond Park & North Kingston. Conservative candidate for Mayor of London Zac Goldsmith’s  campaign, who was supported by a very special guest, Prime Minister David Cameron.

The phone event was covered by the Evening Standard and Prime Minister David Cameron posted this image on Facebook, that was reposted by Zac Goldsmith and was kindly brought to my attention by a good friend.

There were many moments along the international journey to apply Last Responsible Moment thinking. Would the products be completed in time from France and UK to fly Friday to make the Caribbean for Saturday Morning?

Would I make connecting flight on time if I don’t speak to someone about that I have 1/2 hour left to get to next flight.

Will I make it in time to Volunteer, if this taxi continues to be stuck in traffic.

If I take a tube will it be faster than a taxi.

Each one of these decisions impacting a successful or unsuccessful outcome.

Many organisations I introduce Last Responsible Moment Thinking to, get surprised just how revolutionary this exercise is to identify where decisions need to be made and when they need to be made along the Agile planning cycle.

For teams that struggle with getting testing completed by the end of the sprint, or teams that are constantly refining stories in the first couple of the days of sprints Last Responsible Moment planning is truly liberating.

If you would like to know more about Last Responsible Moment and Agile email info@agileachievement.com to arrange a confidential discussion.

Teams that talk Last Responsible Moment, really discover what Agile Transformation means.

b4094a47-98c5-4eef-a9a5-6f787962c49c-medium

Brad Pitt on Agile – MoneyBall Agile Transformation Master Class

Friday, November 25th, 2011

The story of Oakland A’s general manager Billy Beane’s successful attempt to put together a baseball club on a budget by employing computer-generated analysis to draft his players.

Could Baseball really have anything in common with Agile?

Well up until Brad Pitt’s portrayal of baseball manager Billie Bean in Money Ball (I would have said no)

But when you look at this film, and its correlations between any organisation taking on Agile you will soon agree that Hollywood has again produced a 90 minute Agile masterclass.

We follow the trials and tribulations of Oakland & Billie Bean who have a limited budget, limited time and a dream to win. Sounds like a few projects I know, there is a classic scene where Brad Pitt goes to ask for more money, and is advised you have to work with the budget you have. (this is where the creativity kicks in & Oakland go Agile)

Of course there is the moment in the video clip below that also illustrates perfectly the fine balance and separation of duties between iteration manager (IM) & project manager (PM). (watch out for Brad Pitt saying “I never watch the game”)

The principle of Agile workshops are clear to see as well. Highlighting the importance of stakeholder participation in the early stages so that everyone involved in the project is there, despite the project manager’s (Brad Pitt) table manners.

There is a strong sense of iteration management & release planning in this moment when they are reviewing the players refered to as an Island of Misfit Players

There is a championship moment available for any organisation willing to take the leap into Agile, it’s a practice that is clearly working not just in Baseball, but in Financial Institutions, Software Houses, Telecommunications even Lonely Planet Guides.

Fear is one the biggest things faced by the organisation when going Agile.

Agile training is one of the keys to getting the organisation ready and helping people emerge themselves into the principles of Agile so that if the ball is thrown from them in any direction hopefully in time they will relax into the concept of “fail fast early” and be able to adjust adapt get on with the winning rest of the game.

This week we had a group so comfortable they even took their shoes off..

Ladder Goat Your So Random

Tuesday, October 4th, 2011

Story Development & Scenarios

A little while back one of our agile coaches was shown a you tube video, it was of a gamer that had been up for 24hrs straight, and out of the blue appears something most unexpected. Is it a deer, is it a donkey, no ladies and gentleman it is indeed a ladder goat. You see a goat appears in the middle of the battle field, after the game has been played for 24hrs continually.

When the same agile coach studied with the master of story development Robert McKee, in London, to their surprise a number of software developers from a game house in the Netherlands were also learning the craft of story elicitation. Game developers take their stories seriously, and Hollywood take their successful stories from computing games even more seriously.

So when you’re in the midst of your story development BA’s, testers, & Product Owners determining your scenarios, asking why do I need to do this, and wondering why do I need to learn this? Just think Ladder Goat. Especially when you’re getting your head around the concept of Happy Sad, Mad & Bad and why they are important for your narratives.

Warning this video below is contagious, and a couple of words are considered adult content & controversial for the work place environment a couple of minutes into the video, watch it long enough and you too will be laughing, but when we look at this from the Agile perspective, how did the story development for this feature of the game take place? How were the scenarios developed?

%d bloggers like this: