Posts Tagged With: transformational projects

Because “It’s there” is not a good reason to pursue agility!

I’m seeing increased similarities between online hype surrounding agile and the marketing of weight loss products. Losing weight or being agile are being promoted as the main objective when both of these are just a means to an end.

We don’t invest significant effort and cost just to lose weight. We want to feel better about ourselves, look slimmer for others or gain health benefits.

Similarly, agility should never be a goal until itself – we need to define what we are hoping to realize by achieving a higher level of agility.

This is an important distinction.

If our focus is purely on becoming more agile, it can cause leadership teams to define overly ambitious time frames for achieving certain objectives or demanding unrealistic levels of capability given their industry, culture or other context. This is similar to someone who doesn’t attempt to connect their weight loss desires to specific achievable outcomes. Over time, this can cause the individual to engage in obsessive dieting behavior which might leave them worse off than before.

A traditional, multi-product large company undergoing an agile transformation should always aspire to reaching a higher level of capability, but it is doubtful that they will ever be as agile as a new, small startup. I enjoy playing golf and try to set achievable goals for myself each playing season but comparing myself to a PGA tour professional will demoralize me and eventually cause me to give up the game.

When managing projects, it is wise to understand what the relative priority of the constraints on a given project are. If a sponsor indicates that delivering on time is most important, then cost, scope, quality and other constraints could be subordinated to schedule.

With an agile transformation it may be advisable for the supporting leadership team to prioritize their objectives before getting started. Are they primarily focused on increasing customer value, is it about improving quality, cost containment or increasing the engagement and happiness of their team members? It can be very educational to have each senior executive rank a predefined list of such outcomes individually and then have the leadership team compare the differences in perception. This exercise might help to avoid misalignment issues at a later stage of the transformation.

If we don’t know where we are going and why we want to get there, no road will take us there.

 

Advertisements
Categories: Agile, Facilitating Organization Change | Tags: , , | Leave a comment

Does your PMO hinder or help your agile transformation?

An agile project management office might sound to some like an oxymoron, right?

This might be a reasonable assertion as many PMOs were first formed to provide oversight over a portfolio of projects and enforcing standards sounds like the antithesis to agility. But many successful PMOs have evolved beyond governance and control to helping their company reach higher levels of organizational project management maturity, and increasing agility should be complementary and not contradictory to this pursuit.

There are many ways in which PMOs can hamper progress towards greater agility including:

  • Enforcing standards over principles
  • Continuing to apply traditional funding models and prerequisites to agile investments
  • Obsessing over vanity metrics such as velocity or time to market rather than business value delivered or shipped features utilized
  • Evangelizing agile from the ivory tower instead of actively engaging with and supporting teams
  • Failing to inspect and adapt

So what can a PMO do to actively support an agile transformation?

  • Collecting chronic impediments from agile teams, curating and prioritizing them, and championing their elimination by the appropriate senior leaders
  • Having the courage to say “NO!” when a given context is not suitable for using an adaptive approach
  • Advocating for funding to incent early adopters to try new delivery approaches
  • Encouraging staff who possess the right expertise, behaviors and attitude to train and take on Agile Lead/Scrum Master or Product Owner roles with coaching support
  • Examining their own operational processes and leaning them out as much as possible
  • Shifting portfolio reporting from being a manual, onerous process to the automated consumption of information radiators
  • Migrating from an artifact-centric delivery approach to an information-centric model
  • Transforming heavy, gate-based governance to a metrics-driven, exception-based process
  • Working actively with functional managers, procurement, HR and other key stakeholders to change their project engagement models to be more support of adaptive approaches
  • Helping portfolio governance committees to make their investment selection, evaluation and prioritization processes more agile

An agile transformation provides the leadership of a PMO with a good opportunity to review their charter and service catalog – are these still relevant, and if not, what can be changed to ensure that the PMO is not identified as common impediment by agile teams!

 

 

 

 

 

 

Categories: Agile, Facilitating Organization Change, Project Management, Project Portfolio Management | Tags: , , , , | 2 Comments

Are your agile transformation blockers like agents in The Matrix?

Agile transformations are susceptible to a variety of impediments but sometimes these hurdles are not as high as we believe them to be.

In almost any company other than a startup, some or all of the following tangible blockers will not only be present at the beginning of the journey, they may continue to stymie teams years into their transformation.

  • The inability to dedicate primary roles (e.g. Product Owners, Agile Leads) to a single value stream
  • Geographic dispersion and distribution of team members
  • Legacy integration requirements which throttle the pace of continuous integration or continuous delivery
  • Complex compliance requirements
  • Onerous and inefficient procurement policies
  • Labor contracts or other constraints on developing generalizing specialists
  • The lack of comprehensive automated test suites or similar accelerators
  • Delivery and control partners who cannot be influenced to transform their delivery models

Are these likely to disappear quickly? Not likely. Some such as technical debt or legacy integrations can be eliminated over time with persistence and sustained investment but others are a natural by-product of a company’s industry, the free market or globalization.

So when I hear teams complaining about these blockers during their daily stand-ups or in their retrospectives I recall Morpheus’s exchange with Neo at the beginning of The Matrix.

Morpheus: To your left there is a window: open it… use the scaffold to get to the roof.
Neo: No way. No way. This is crazy.
Morpheus: There are two ways out of that building: one is that scaffold, the other is in their custody. You take a chance either way: I leave it to you.

Neo’s fears and doubts are more crippling than the lack of a dumpster below his office building which he could jump into or a fire escape ladder close at hand to get to the roof.

As the movie progresses, Neo continues to struggle with overcoming these constraints and Morpheus continues to coach him: You have to let it all go, Neo. Fear, doubt, and disbelief. Free your mind.

But Morpheus, like agile coaches, can only show the way.

Teams, like Neo must walk the path themselves. Once Neo understands the Matrix for what it is and embraces his place in it, his perception of limitations including agents evolves such that he no longer perceives them as great a threat as he and others make them out to be.

Once teams successfully adopt the right mindset, they can respect the impact of organizational blockers but continue to discover ways of being agile.

 

Categories: Agile, Facilitating Organization Change | Tags: , , | Leave a comment

Blog at WordPress.com.

%d bloggers like this: