Category: agile (page 2 of 2)

Agile from the eyes of a 20 year PMP veteran – Leading from Behind

One of the biggest challenges for Project Managers in making the transition to Agile has to be the way that they need to do their daily job.  The PM is typically the leader of the project, the one that sets the pace and direction, that makes all the key decisions to ensure that the project is finished “On time and on budget”. This changes when they work on an agile project as they are not in front of everyone directing what everyone is doing and creating report after report.

A project manager is responsible for the 5 stages of a project: Initiating, Planning, Executing, Monitoring & Controlling, Closing. They take responsibility for the project and nurture it and the team to get the required result.  The PM is used to, in fact instructed to be the guiding hand of the project, ensuring that the project is completed as per the PM’s wishes.  The PM has to lead in order to do their job.

Contrast this with the role of Scrum Master or even the Product Owner.  Each of these roles has a responsibility to make sure the project is going smoothly and that the team is operating at its optimal level.

The Scrum Master is not the leader of the project, but they do play a crucial role. The Scrum Master is more of a coach for the team, helping them produce the work, but they don’t manage the team.  The responsibility is more towards making sure that the Scrum process is followed, removes roadblocks and supports the product owner.

Not everyone can make the shift from PM to SM, and many just shouldn’t even try.  The mindset and skills to lead from behind is much different than the PM’s direct managing/ordering work done.  In order to make the transition a PM would have to let go of their ego and realize that the project does not revolve around them, but instead it revolves around the team.

It seems that a Project Manager is like a babysitter and they treat the team like a bunch of children; if they don’t do what the PM says they get in trouble, they have do bet watched at all times, you need to report to management (the parents) what the team is doing, the PM mediates disputes, and if something bad happens the PM is blamed.

The Scrum Master, however, is more like the coach of a professional sports team; everyone knows their role and is eager to do what they do best, the SM guides the team and keeps them aware of the rules, each member of the team helps other members collaboratively and the success of the team is shared equally.

Being a SM is more about enabling the team to do their best work possible and removing any barriers to success.

 

Another benefit of Agile

When I ran a team, there was the need for weekly or at least monthly, staff meetings.  Not to, as the comic suggests, get my ego stroked but to make sure everyone was up to date with what everyone else was working on. With an agile team, we are all acutely aware of what we are working on so the only updates that the team needs is on how the company is doing, and I provide that information on demand.  Another great agile benefit.

Staff Meetings

This would be the wrong outcome of Agile

 

 

While I did my MBA this was definitely one of the outcomes.  However, working on an agile team has changed this. You have to trust your team. You quickly learn that everyone is professional and trying their best to do the job.

group projects

Agile from the eyes of a 20 year PMP veteran

My world has changed, for the better.  When I first was introduced to Agile it was just a buzzword at a large company. “We need to be more agile. We need to set up agile teams.” Okay, sounds easy. Let me put together a project plan for that. It turns out that we were just paying lip service to an idea that someone told the CIO about. When we had to actually do agile, there was no support, no plan, no idea of what we were supposed to be doing. I had a team of 6 developers working on web projects that reported to me.  A great opportunity to actual put an agile team in place, however were told to “Keep Calm and Carry On”

Keep-calm-and-carry-on

Fast forward a year and I’m now part of an agile company and working closely with an agile team. There are many differences, all of which take some getting used to.

Over the next several posts I will examine some of the major differences:

  • Leading from behind
  • Where does the work of the PM go?
  • No Project Plans
  • “Meeting Hell” removed
  • Visible, daily updated progress
  • “Requirements? We don’t need no stinking requirements!” (with all apologies to The Treasure of the Sierra Madre)
  • Weekly/Monthly Status reports: guessing versus actual metrics
  • A reason to invest in 3M -> Post-it notes everywhere

The thousands of dollars spent on attaining my PMP are not necessarily wasted, but they are diminishing in value for my future.  Sure I can still talk the talk, but I no longer want to walk the walk.  In the words of Pumbaa from the Lion King “You’ve got to put your behind in your past”, basically it is time to move forward with something that is better, stronger and faster in delivering results.

 

SEC awards Accenture 5 year contract to improve their websites

Wow. “The U.S. Securities and Exchange Commission has awarded Accenture Federal Services a five-year, $13 million contract for major architectural improvements and redesign of its three public websites, online tools used most frequently by the public, and the agency’s employee intranet” (source)  That seems like a lot of money and a very long time to do some redesign work.  I realize that the sites get 35 million hits per day combined, but as someone who has recently converted to agile project management, this seems like a very old school way to do this work.  

Newer posts

© 2017 Lee News

Theme by Anders NorenUp ↑