Showing posts with label communication. Show all posts
Showing posts with label communication. Show all posts

Wednesday, May 28, 2014

Traditional Project Management vs. Agile Project Management: Week 7

How the heck are you supposed to have an up-to-date status of your team’s needs, let alone an up-to-date status of project progress? 

As of last week, we have twice-a-week scrums on Tuesdays and Thursdays.  I can glean only a smattering of what the team is working on at these meetings since said meetings seem to morph into I-have-a-problem or I-can-help-you meetings.  This format is actually great for this team since they aren't communicating otherwise.  I see very little email traffic.  I hear very little of anything, really, and I find that I’m pulling information from reluctant teammates.  I pushed for a daily scrum, but many people – including my project sponsor – balked at that idea. 

So in light of the fact that I was not having any daily meetings until last week (sort of), I resorted to using the weekly status meeting that the project sponsor set up.  I asked how I thought we were tracking and then asked about blocking issues.  To my surprise, the project sponsor wanted these meetings to be about the PM (me) reporting to the team how things were going.  I find this very limited, and I end up getting updates from the team anyway. 

I’m learning that Traditional Project Management is more about going to each person on the team – daily, if need be – and asking them how they’re doing or where they’re at.  While this can be great from a relational standpoint, it can also be detrimental.  The PM eventually becomes a pest in the eyes of his/her teammates instead of being a trusted source of roadblock-removal.   In an environment like the one I’m in, the fact that these teammates are matrixed resources who are far too overloaded doesn't help me when I have to ask them about the status of the project for which I am responsible.  They are not happy to see me, so this immediately drives a wedge between us that is sometimes difficult to pry loose. 

Gathering status one teammate at a time is also a waste.  By the time I get status from everyone, the status of the first person I talked to has changed.  Also, if I hear of roadblocks, then I have to bounce around from person to person to see if I can clear the roadblock before it becomes an issue.  This is why I think daily scrums are so valuable.  We can get everything out of the way all at once and keep the team moving forward one day at a time.    

Don’t even get me started about the tools we’re using to track progress.  We have a very high level project schedule in Smartsheet.  If you aren't familiar, Smartsheet is an MS Project clone that is all online.  We then have a “test control sheet” that lists high level test case names.  (Remember my post a few weeks ago pondering the reasons why I, as a PM, was required to put together a test plan?  Yeah, this “control sheet” was the end result of that.)  On top of the “control sheet,” we have test scripts and individual test plans we’re updating.  I have to peruse all these places to see where things are and then somehow keep track of it.  I've created a private Trello board just to keep all of this straight.  I would much prefer that we had everything tasked out… user stories… something!  This is what we have, though, and I have to work with it.

While I think Traditional Project Management definitely has its place, in the software world, Agile is a much more efficient way of getting things done.   

Wednesday, May 7, 2014

Traditional Project Management vs. Agile Project Management: Week 4

So in my current role of PM, I'm experiencing the NEED to babysit EVERYONE on this project far more than I have in the past as a Scrum Master.  Here are some examples:

  • No one is sharing information even after I've requested it.  I have to pull it from them.  For instance, I had no idea that two of my "testers" were even available for my team.  I find myself digging for documents after I've asked people to share them, too.  
  • Expectations are completely unclear.  For instance, I just learned that I - as in ME - need to put together a test plan.  For you traditional PMs out there this probably isn't new for you, but I've never done this before.  Why?  Because I had self-organizing, cross-functional teams that took it upon themselves to take care of this crucial tidbit.  Now I get the unsavory task of asking everyone to document what they're doing so far.  
  • Communication seems incredibly stifled since we don't yet have daily stand-ups.  For instance, dates (such as whether or not we'll have to work over the 4th of July weekend) have been up the air for at least two weeks. AND dare I mention the tester availability thing again?    
What are some differences you've noticed and how did you manage them?  I'm feeling like a fish out of water in this more waterfall type of environment (yes. pun intended.)

Wednesday, April 30, 2014

How Transparent Are You?

I had the good fortune to attend Mile High Agile this year.  It was held on April 18th at the Downtown Denver Marriott, and it was a packed house!  The company I work for as a consultant, Sogeti, was a Gold Sponsor, so I had the opportunity to attend the conference and rub shoulders with some industry experts.  I attend some great seminars, shared some thoughts, and learned quite a bit.  Not too shabby for a day’s work, right?

Of course I attended the keynote this year: The Future of Agile (If There is Any) by Robert “Uncle Bob” Martin.  He had a lot of insight, and it was very eye-opening to hear from one of the people who actually crafted the agile manifesto in Snowbird, Utah in 2001.  He said a lot of things (including mapping out the history of the world on the breadth of his arm span), but one thing that really resonated with me was transparency.   

“Uncle Bob” said that the whole meaning behind what the folks in Snowbird meant to convey was transparency.  He spoke of the disconnect between businesses and the people doing the heavy lifting (i.e. developers and testers).  That disconnect created distrust because neither side could see what the other was really doing.  As a result, they didn’t trust each other.  Developers and testers were held to “estimates” as if those estimates were written in stone, so they fudged their numbers.  Business folks expected them to fudge so they didn’t share all the information with them (like the big picture). 

I wrote all of that in past tense, but really, do we see anything different today?  That chasm between business folks and developer/tester folks still exists.  I think we have some bridges across it now, and by using agile practices, we can certainly build more.

Mr. Martin also went on to illustrate this disconnect in terms of training being offered and in terms of percentages of people who attend conferences like Mile High Agile.  Of the folks at the conference, a very large percentage of them were managers of some sort (project managers, scrum masters, agile coaches, etc.).  A much smaller percentage were developers and/or testers – the technical types.   Daniel Lynn illustrated this pretty well in one of his recent blog posts on Coyote Agile.  Go check it out. 

So how do we fix this?  I think the first step is to ask ourselves this question: How transparent are we?  I’ve asked this question about a good many places I’ve worked, and as can be expected, some companies have been more transparent than others.  Here are a few of the transparent practices I most appreciated:

On Projects / In Teams
  • Regularly communicate status
  • Regularly solicit feedback
  • Regularly schedule demos of ongoing work
  • Promptly raise roadblocks
  • Publicly share successes
  • Regular communication about work in the form of Daily stand-ups
  • Managers communicate regularly with direct reports (one-on-one meetings are best, but even regular check-in emails are better than nothing)
  • Direct reports solicit feedback from managers and customers (both internal and external)
  • Publicly post/relate team progress

In Departments/Business Units
  • Regular communication from Directors/Executives to convey the big picture
  • Directors/Executives share timely, pertinent information
  • Directors/Executives Publicly celebrate successes, no matter how small

While most of this revolves around communication, there are many other ways we can be transparent.  What are some of your suggestions?