Scrum Burn-Down

Have you ever used a scrum burn-down chart?  Funky name, huh?  It’s actually a pretty handy line chart.  The image below is an example from Standard Time®.  There, it’s called a project history chart. On the X axis, you see time (weeks, months, quarters).  On the Y axis (vertical) you see the number of remaining hours for your project.  As work is applied to the project, it burns remaining hours down to zero.  Team members can see the downward trend and predict when the project will finish.  This is the “light at the end of the tunnel” chart that helps people push for completion.  Show this in your scrum sprint meetings, and your team members will take heart.   Scrum Burn-Down Chart  As you can see, there are some up-ticks as well.  Those represent project scope changes.  Some bright individual decided the project needed a slowdown, and added some additional tasks.  Do that at your own peril, because this chart shows all. –ray

What’s In It For Me?

Something finally occurred to this week.  People care (mostly) for themselves.  I’ve been observing some people recently, and have noted their project participation.  When there’s something in a project for them personally, they go gangbusters to finish it.  And when there’s nothing, they lose interest and quit.  At least, mentally that is.  Be it financial gain, or street cred, or just looking good.  There must be something in it for them.

I may be a little slow, but I had never really studied this aspect of human behavior.  I just thought people worked hard for their company and that was that.  Not so.  They work strictly for themselves.  And now that I look back on my career, I see the same pattern.  My own career was carefully crafted to climb the ladder of success.  If a project didn’t fit that model, I found a way out.  If it did, I worked it for all I was worth.  I wasn’t greedy with my time, but eventually gravitated toward projects that benefited me.  That’s not selfish, it’s just natural.

Knowing that gives me something to work with.  It means I must find ways to help people succeed in the projects I expect their help with.  I must find a clear benefit for each team member.  If there’s nothing in it for them, I should expect them to grow disinterested and mentally quit.  Sounds like a real challenge!

 

–ray

My Manager, When Projects are Late

Being consistent in your management style and personality is important for success. One of the first lessons in parenting is being consistent.  If you discipline your child one time for something, but then ignore that same thing a different time, you are sending a confusing mixed message.  Obviously, your project team members are not children, but the principle still applies.

Our teams depend on us for leadership and direction. As managers, if we are on a roller-coaster of emotion, our project teams will be all mixed up.


My manager when projects are late

Inconsistent behavior stifles creativity and does not allow a tolerable environment for ideas to be exchanged.  If a team member is not sure how you will react from one day to the next, they are less likely to be forthcoming with ideas and suggestions.

No matter how crazy a project becomes or how much stress leaders are under, we must be the model of consistency.  Like the commercial says, “never let them see you sweat.”

 

–Warren

Define: Feature Creep

Feature Creep: Small product feature additions that unexpentantly expand a project scope.

 

Feature creep is one of the big reasons projects ship late.  Some people simply cannot deny themselves.  They want more and more features in their great new product, and can’t stop adding them  Here’s how it happens.

When a new product feature is complete, there are oohs and aahs from all the project stakeholders.  They love it!  Why?  Because they are sure customers will find it useful and reward the company with more business.  That’s only natural.  But then something else happens…  One of the stakeholders steps up and says, “That’s cool, but can it do one more little thing?”

All the other stakeholders agree.  The new feature you added is nice, but the product should do one more thing to be complete.  And they may be right.  So you add that.  And a few more things.  And a few more things after that.  That’s feature creep.

Little additions creep into your product features until they consume a major part of the project timeframe.  The extra features are nice, but can you afford the extra time?  After all, you now have less time to implement all the other cool features you were asked to do.

Stakeholders often don’t understand this problem.  Later, they’ll come around and ask why your project is behind schedule.  You can’t say that it’s because of all the little things they asked for.  Why?  Because they won’t remember those or they don’t see them as a major time sink.  See the problem?  You can’t win with feature creep.  🙁

 

–ray

How To: Calculate Costs in Microsoft Project

This post will illustrate how to calculate costs in Microsoft Project.  As you will see below, each tasks has a total cost and an actual cost.  The actual cost are those costs that have actually been incurred during the execution of the project.

Costs in Microsoft Project and Standard Time® are very different.  Each task in Microsoft Project may have an arbitrary dollar value.  We’ll assign some below to demonstrate.  This is not true of Standard Time®.  Standard Time calculates task costs by multiplying hours times rates.  (C = H * R)  There are various rates a project may have, but the formula is always true.  Microsoft Project is different.  Follow the steps below to calculate costs in MSP.

Create some tasks:

  1. Add a task named “Task 1”
  2. Add a task named “Task 2”
  3. Set the Duration to 100h and 40h respectively
  4. Remove all columns by the Duration column (right-click and choose Hide Column)

 

The results look like this:

 

Insert the following columns:

  1. Cost
  2. Actual Work
  3. % Complete
  4. Actual Cost

 

The results will look like this:


Microsoft Project Cost Fields

 

Experiment with the Duration, Cost, and Actual Work fields, and you will see updates costs values.  The image below illustrates this.


Updated Microsoft Project Cost Values

–ray

Advice: Get Corporate Buy-in

Project Management Advice: Get Corporate buy-in for your projects.

In other words, make sure the corporate executives are active stakeholders in your project.  I suppose this goes without saying, but I’ve seen lots of projects where this is not the case.  Project teams somehow come to the conclusion that their project will be funded and accepted, even though corporate has not explicitly said so.

Just because your team is developing a new product or in-house tool, doesn’t mean corporate will stand by you.  Without vested stakeholders at the highest level, your project could easily be canceled.

The name “Harold” comes to mind when thinking of this subject.  I worked with a man named Harold who was researchinig a product for his company.  Months went by as he studied the features and benefits.  He eventually took a job with another company and I discussed the project with his boss.  His boss said he never knew what Harold was up to, and had no intention of adopting the product!

 

–ray

Project Managers are Coaches Too

Many people know that Phil Jackson coached 9 teams to NBA titles and Bill Walsh was a football genius with many Superbowl wins.

Do you ever hear about Project Managers who take multiple million-dollar projects to the finish line and bring home the victory?  Of course not, but they are critical in setting the tone of a project, defining clear objectives, and pushing all the right buttons to get a Project Team on the same page to accomplish their project goals.

People alone, with all of their various personalities, are tough to manage.  Project Managers are responsible for setting project task dependencies, trying to stay within project budgets, and work to keep a pulse on all the project resources.  Man, that is a lot of responsibility!

In sports, coaches use video tape, advanced scouts, and many other tools to accomplish their goals. In the project world, we use tools like MS Project or a good time tracking/project management tool such as Standard Time® software. Standard Time automatically e-mails Project Managers if a timesheet is insufficient and will warn a project team if a project is over budget.  It allows you to visually manage your resource allocation. It is a very effective tool.

The bottom line is that championships are not only won by pushing the right buttons. The foundation for winning starts with having the right tools. Are you still using antiquated spreadsheets and verbal discussions to win your championship?  If so, you may be setting yourself up for failure.

–Warren

How To: Display WBS Codes in MS Project

This post discusses how to display WBS codes in Microsoft Project.  WBS stands for Work Breakdown Structure.  It is an (arguably cryptic) way to number tasks in a project so you can tell the hierarchy position.  The first number in the sequence represents the task id.  Each dot represents a subtask.  Follow the steps below to show the WBS number.

  1. Enter three tasks
  2. Right-click in the column header area
  3. Choose Insert Column
  4. Choose the WBS column
  5. The results will look like this

 


WBS Codes

 Next, we’ll insert some new tasks and demote them.

  1. Right-click in row #2
  2. Choose New Task
  3. Enter some tasks
  4. Demote them
  5. The results will look like this (notice the WBS codes)

 


Indented WBS Codes

 

If you really want to make your WBS codes exotic, try these steps.

  1. Choose Project, WBS Codes…
  2. Enter a prefix
  3. Choose a custom numbering scheme
  4. Click OK
  5. The results may look something like this

 


WBS Prefix

 

–ray

Question: Why Do Projects Cost More Than Expected?

There are a lot of possible reasons for this.  I’ll enumerate the reasons why I think projects cost more than expected, and then discuss the most probable ones.  Let me know what you think!  Got a few more reasons?

  1. Forgotten tasks
  2. Unknown tasks
  3. Customer expectations change
  4. Feature creep

My biggest issue is always ‘forgotten tasks’.  In my experience, forgotten tasks results in project cost overruns more often than any other reason.  People tend to throw out a cost before they have listed all the work involved.  Halfway down the road, they remember 25 – 50% more tasks.  That adds up!

Sometimes, one thing leads to another.  Tasks that you didn’t know about pop up.  What are you going to do when that happens?  You can’t just abandon the project.  You have to eat the extra work and absorb the cost overrun.

Once your customer gets a look at the product, he may have a few new ideas of his own.  He may see something he likes, and feel free suggest some additions.  Those add up too.  Just make sure he knows that he must absorb the additional project costs.  Otherwise, you’ll end up eating that too.

Feature creep happens when customers and developers like what they see and want a little more, and little more, and a little more.  Before you know it, there’s an extra 10% cost in the project.  Yikes!

–ray

Computer Jobs Hit Record High

Last week CIO Insight reported that IT jobs had reached a record high (four million IT workers), and IT unemployment had fallen (2.3 percent).  That’s phenomenal!  See the link below.

 

http://www.cioinsight.com/c/a/Workplace/Computer-Jobs-Hit-Record-High/

 

Okay, great news, but why is IT spending down?  While I have no hard facts, I have my theories.  Bear with my madness while I explain.  Post a comment if you don’t agree!

1. It’s summertime.  IT spending falls when the temperature rises, and rises when it falls.  November, December, and January are traditionally big months.  June and July…  Well, they are another story.  🙁  People are out and about, and they don’t want to worry about buying stuff.  They’re too busy checking out the next vacation spot on the web.  Yikes.

 

2. Gas prices.  People bring their personal woes to work.  Got trouble filling your tank?  Then you won’t spend money at work either.  What, you say?  There’s no hard connection between the two.  No, but there is an indirect one.  If you’re worried about finances at home, you’ll worry at work as well.

 

3. Too many salaries.  Or, perhaps spending is down because there are too many mouths to feed.  That’s always a possibility, but I suspect it’s the other two reasons.  We’ve had other times with low unemployment, and high spending.

 

–ray