Posts Tagged With: Process compliance stupidity

Lessons in agility from wine tasting…

One of the benefits of living in the Greater Toronto Area is being less than an hour away from a large number of good wineries in the Niagara region. A few past colleagues of mine got together for a morning round of golf and followed that up with a wine tasting and a hearty lunch at Ridgepoint Wines (thanks for the recommendation, Brendan!). After enjoying a glass of their 2010 Reserve Meritage I came to the conclusion that wine tasting and agile have more in common than you might think.

It helps to have a guide

You could certainly partake in a flight of wine with friends without the benefit of a sommelier, but you won’t enjoy the experience as much and you might learn some bad habits such as not giving your wine a chance to breathe or drinking without sniffing the bouquet. Similarly a coach can help steer a team past anti-patterns so that they have a chance to appreciate what agility truly is.

Start small and grow from there

For novices, visiting more than one winery in a day could be a recipe for disaster. Without having developed the discipline to pace themselves they run the risk of getting tipsy too quickly and might get turned off by the experience. Starting with a large project is inadvisable for novice teams – they won’t possess the discipline to scale their behavior and practices and might blame agile rather than their immaturity.

There is no one right way

While there are good principles for enjoying wine, don’t let anyone try to convince you that you must follow pairing guidelines. While a robust red wine might be a good match for a meat dish, if you enjoy its flavour there is no reason you can’t have it with any other type of cuisine or even on its own. User stories are a good approach to starting a conversation about functional requirements, but don’t be bullied by agile wannabes who insist that all requirements must be captured as stories. Like with any practice, context and culture count.

Teams doing agile might make you want to drink but I prefer to have the perspective of the (wine) glass being half-full.

Categories: Agile, Project Management | Tags: , , | 1 Comment

All form and no (agile) substance?

Plus ça change, plus c’est la même chose

Jean-Baptiste Alphonse Karr’s warning reminds us that it is very easy to ignore the Manifesto for Agile Software Development’s value statements.

We might have done away with heavy project governance, premature or excessive planning, and documentation for documentation’s sake, but if we don’t remind ourselves why our team performs specific agile ceremonies, we are no better than our brethren toiling under the burden of traditional, one size fits all delivery practices.

Let’s start with sprints. Short time horizons should focus our efforts towards delivering value early and regularly while having fixed time boxes enables forecasting when we should be able to complete a release. But if we start treating sprints as phases (e.g. development, testing) or we batch work items within sprints in a waterfall manner, we haven’t really gained benefits from this approach. Similarly, if we don’t respect sprint end dates or we regularly modify the duration of our sprints we can’t forecast effectively.

How about your daily standups or scrums? These are meant to serve as micro-planning opportunities to align team members towards accomplishing sprint goals. They also provide an opportunity to surface blockers in a transparent, safe fashion to ensure these get resolved in an efficient and effective manner. But if team members are absent, we don’t start or end on time, one person monopolizes the discussion, or they turn into status meetings, why hold them at all?

Velocity enables teams to assess their throughput sprint over sprint. Used correctly and with the right underlying discipline on work sizing and backlog management, velocity can help a team forecast. But obsessing over velocity is as bad as focusing on percentage work complete in traditional approaches. When abused velocity leads to progressively reducing quality, erosion of team morale and unhealthy comparisons between team members or teams.

Showcases or demoes give a regular opportunity for key stakeholders to view what has been completed, to provide feedback to ensure that what is delivered meets customer needs, to maintain sponsor commitment and to provide a forum for visible recognition of the team’s hard work. But holding these ceremonies when there is nothing meaningful to demonstrate provides limited benefit to the invitees. Having the agile lead or other team member be the only person conducting the demoes doesn’t give everyone a chance to have their day of glory. And having team members get defensive when constructive feedback is provided about a feature which doesn’t quite hit the mark is just going to further the gap between the delivery team and the customer.

Meet the new boss, same as the old boss” – Pete Townshend

 

 

 

Categories: Agile, Process Peeves, Project Management | Tags: , | 2 Comments

Agile transformations should lead with changing mindset and behavior rather than practices

Like most North American kids growing up in an urban environment, my son learned to drive cars with an automatic transmission. Now that he’s been driving for a year, I’m starting to teach him to handle a manual transmission. While the most visible aspect of this is shifting, the exquisite art (to quote the Bride) lies in the proper use of the clutch. Once a driver develops the feel for a clutch and is able to find that sweet spot between dormant and stalling so that they can get a car rolling without the use of the gas pedal, the rest is mere mechanics.

Golf presents a similar scenario – learning to swing a club is secondary to mastering weight transfer. Through practice, once that skill becomes second nature, the rest of the swing will come. But if we start with the top down approach of learning to swing using the shoulders and arms, it will take much longer to develop a good swing.

Agile works much the same way.

Just because we divide our project’s timeline into sprints, conduct daily standups and bi-weekly retrospectives and ask our teams to self-organize, if the underlying behaviors of senior leaders, mid-level managers and team members don’t change, we are just putting lipstick on a pig.

Behavior and mindset changes don’t happen overnight and it’s not easy to confirm what has changed the way one can when introducing a practice or tool change.

This reinforces the importance of a change strategy for all levels of stakeholders involved with the project. While they might appreciate the benefits of agile delivery, if they haven’t reflected on the mindset changes required, stakeholders will act like chickens when we’d need them to be pigs. Senior leaders, delivery and control partners need to understand how they will need to adapt before they are put on the spot to support an agile project. Embracing the change won’t happen overnight which is why effective coaching is required to enable them to become the advocates we need to champion changes with their peers.

The challenge is that there is usually a demand to demonstrate value from a change in delivery approach within a reasonably short time.

That is why it is best to start with one or two small projects to provide a safe opportunity to try, fail, learn and improve.

Start with practices and tools and Cargo Cult behavior is almost a guarantee.

Categories: Agile, Facilitating Organization Change, Project Management | Tags: , , | 1 Comment

Blog at WordPress.com.

%d bloggers like this: