Posted on

What is a project milestone?

Good question!  What is a project milestone?

Think of a project milestone as a marker in time where you stop and evaluate your project.

How is your project going?  Have you completed everything necessary to move on to the next level?  Have you finished everything in this milestone?  And are you ready to move forward to the next one?

The video below shows what milestones look like in a Gantt chart, and how to track time to them.  But normally you don’t actually track time to milestones.  They are just markers in time, not actual tasks.  But you can if you want to.  In fact, you could set up a project with nothing but milestones!  Just track hours to them and compare against your original estimates.  That’s a simple way to track projects.

In the old days, a milestones was a physical stone erected by the road.  There would be one stone every mile.  Just count the stones as you waked along, and you would know how far you had traveled, and how far the next town was.  They were just like our interstate mile markers now.

Project milestones are very similar.  They tell you how far into the project you have traveled.  Got a big project?  Put up a milestone every so often and you’ll know where you are.

Posted on

8 Dirty Secrets of Project Tracking

The video below may be useful for some.  Ray White of the Standard Time® Timesheet team outlines eight dirty secrets of project tracking.  These make a lot of sense.  Take a look!

 

What did you think?  Project tracking is a slippery game.  You’ve literally got thousands of enemies and obstacles that will bring your project down.  It takes a watchful individual to make sure those things don’t happen.  And a project manager who can do that is worth their money.

I was once on a project where the manager made us all sign a paper that said we’d finish the project by a certain date.  It was a big event where the paper was passed around for all to sign.  Honestly, most just laughed, signed, and mocked him later.  Here’s why: he never followed up with any real management.  He committed virtually every sin in this video.

Even though we signed the paper, he had no real end-game plan.  We just all worked on stuff we thought was cool.  The project blew through the ship date and died an ugly death from suffocation.  He didn’t track our hours.  He let the cool kids camp out on tasks they liked, which left the rotten tasks unfinished.

I never really know when the product would ship because it was always a moving target.  And like I said, the project died of suffocation months later.  Hummph.

Hey, I found the video transcription on this page.  Hope it helps!http://www.stdtime.com/videos/dirtysecretsofprojecttracking.htm

–newshirt

 

 

 

Posted on

Microsoft Project Task Usage View

What is the Task Usage view in Microsoft Project?  The simple answer is: a daily breakdown of the hours for each employee. You’re probably familiar with the ‘Work’ and ‘Actual work’ columns in the Gantt view, right?  The Task Usage view just breaks those numbers down by day.  The video below illustrates that perfectly.


Standard Time® with MSP Task Usage

So let’s assume you have a task with 100 hours scheduled to you and another employee.  That 100 hours is in the ‘Work’ column in the Gantt view.  (Ignore the ‘Duration’ column for sake of easy explanation for now.  It has a different purpose.)  The ‘Work’ field tells how many hours the resources are supposed to work.  Here’s a picture of how that task looks in the Gantt view and Task usage view.

Gant View with Work Hours

And Task Usage View:

Task Usage View with Work Hours

 

These two screenshots clearly show the 100 hours for our example.  The Gantt view shows the aggregate while the Task usage view shows the daily breakdown.  Now watch what happens when we add ‘Actual work’ to the mix.  The Task usage view lets you enter hours for the exact day they occurred.  And again, the Gantt view shows the aggregate hours.  (The video above shows an automated way to enter those actual work hours.)

Gantt View with Actual Work

Task Usage view with actual work

 

Of course the automated way to enter these actual work hours is a timesheet.  (I like Standard Time® at www.stdtime.com.)  Employees use a variety of tools to enter and check their own timesheets.  Once correct, all the actual work hours from the timesheet are transferred to the Microsoft Project Task usage view in one quick session – all employees, all at once.  Pretty cool, huh?

–newshirt

 

Posted on

Feature Delays Mean Reallocating Resources

Has a customer of yours ever forgotten to get back with you about a feature you were developing for them?  They were hot to finish, but then weeks went by and no word.  Maybe the feature was almost finished, and you just needed a little more information to complete it.  One phone call or email and it would be finished.

But guess what happens when these delays occur?

All the feature nuances you kept in your head are now slipping…  A week goes by… Two weeks…  A month…  By now you’ve forgotten some of the little details that made finishing the feature so simple.  You’ll have to relearn some of those and get the feature back on track.  What would have taken a short time to complete will now take four times as longs.

When this happens, you are essentially reallocating resources to complete the job.  In some cases when too much time has elapsed, you might just as well restart the project and reschedule hours to come up to speed.  All that admin scheduling take time too.

Moral of the story: Don’t let these little delays creep in in first place.  Stay on top of your dependent resources so they don’t leave you with a long forgetful delay.

Posted on

Ten Tools For the PMO Office

Now, this is what the PMO office needs.  Have you seen this?

The video below lists ten cool tools for the project management office.  (Actually the term “PMO Office” is a little redundant.)  But I really liked this set of tools.  You start with a database that displays all your projects as peers — no more discreet files on your hard drive.  Under each project is a list of assigned to employees.  Those employees see only their projects and tasks in the timesheet where they record actual hours.  Go back to the project task view and you can compare estimates with actuals.

Of course, the PMO office wants more than a simple task list.  They want resource allocation, project revenue projects, utilization reports with percentages and effective rates.  And they want some daily scrum status.  To me… it all seems to be here.  Take a look!

Video: http://www.youtube.com/watch?v=SVJ1AYCJ9Rw

 

Posted on

Homemade Products Don’t Sell

Here’s just a quick reminder that homemade products stick out like a sore thumb.  Have you ever encountered a product that was clearly not professionally produced?  They just look awful, and one look at them screams, “Homemade!” or “Unprofessional!”  It doesn’t take long for consumers to sniff you out and flee.

Epic Fail

This past weekend, my wife and I stayed at a little ‘mom and pop’ motel in a little town in Colorado.  With one step into the room, I got a good reminder of this issue.  (See the pics below from my crap phone)  The entertainment cabinet was hand-painted, and looked awful.  I nearly fled the room, but decided the cost was cheap enough to entice me to stay.  It turned out fine.  But ugly little piece of artwork really drove this point home to me.

Consumers do not like hand-crafted products.

Epic Fail 

Let’s face it… we live in a consumer-oriented world.  Almost every product we touch is machine made, and professionally crafted for maximum emotional indulgence.  Think about the indulgent products you use on a daily basis: $50,000 automobiles… iPhones… stylish eyeglasses… jewelry… and more.  Every product we use it slick and well-designed.  So consumers are used to those kinds of products.  Now slap and homemade software product in front of them, and watch them flee!  Or a poorly polished plastic drinking cup… or any other product you can imagine.  Consumers expect high quality.

This issue is especially true in software, where programmers are sometimes responsible for developing the entire product from code to help files to graphics.  Software developers just don’t have the talents for all those jobs, and it’s very obvious when they try.  The results are a lot like the Riviera Motel.  Can you guess where it’s located?

Epic Fail

Posted on

You Can Never Leave Your First Love

I do not believe a man can ever leave his business. He ought to think of it by day and dream of it by night.

— Henry Ford

That has certainly been true in my life.  To me, business has been something deeply ingrained in my life.  For many years, I wrote code on Christmas Day, New Years Day, Independance Day, and many other holidays.

Yes, I loved it that much.

I would do events I called “24-hour weekends” where I would start coding at 7 AM each morning and go straight until 7 PM on both Saturday and Sunday — two twelve hours days.  And then I would resume my normal 60-hour week on Monday morning at 5:30 AM.  That’s how much I loved my business.

Things have changed a little since I’ve gotten older.  Economic downturns turn you hard.  Turn you bitter.  Make you cynical.  And you say, “What good was all that work?”  So yes… I’ve had times where I’ve quit and vowed never to do that again.  I’ve actually quit my business several times.  But like a dog to his vomit, I’ve always returned.  And after doing that a dozen times, I guess I’m here for the duration — a lifer.

I still love my business.  The current economic doldrums put a severe throttle on my work efforts.  It’s awfully hard to put your life into something (and that’s what Henry was really saying in the quote above) when customers don’t reciprocate with any degree of appreciation.  But I still work hard.  I might even pull a few of those 24-hour weekends from time to time just to remind myself of the love I still have for my business.

Posted on

10 Best Teams – My Comments

Below is a short commentary on a fun article I recently read.  (See link below.)  The Online Business Degree put together a list of the best teams ever assembled.  I read through the list and agreed with most.  Some sounded a little contrived, but workable.  Here are my reactions.

http://www.onlinebusinessdegree.org/2012/08/29/the-10-best-teams-ever-assembled-and-what-we-can-learn-from-them/

I’ll take each team in order:

1. The Dream Team:
Yes, they were the finest basketball team ever assembled, but they were also professionals.  I thought the Olympics was supposed to be amateur.  I vaguely remembered a guy named Jim Thorpe losing his metals because he was accused of accepting gifts.  I’m behind the curve on this; maybe The Olympics has turned pro, and I missed it.  But the Dream Team always seemed odd to me.

2. Sherlock Holmes and Dr. Watson:
Sir Arthur Conan Doyle created Sherlock Holmes and Dr. Watson as fictional characters.  They weren’t real.  But they sure had some fun adventures, and the recent Hollywood film is pretty good.  Doyle presented them as pretty good team, I must admit.  Still… it’s hard to get behind them as a real team.

3. Rogers and Hammerstein:
Now here’s a great team!  Nothing fake about them.  This was some of the greatest music of the Twentieth Century.

4. SEAL Team Six:
Worthy of our worship (figuratively speaking).  Have you seen how SEAL teams are trained and formed?  Watch the documentary some time…  It’s amazing!!!

5. The Beatles:
Yep, I’d go with them too!  Millions of people around the world still listen to their music.  But “more famous than Jesus”?  I don’t think so.

6. 1985 Chicago Bears:
Don’t know much about sports, so I can’t comment much.  But hey… if they won a Super Bowl they had to be pretty good.

7. The Justice League:
Another fictional team.  Humm…  I’m not convinced fictional teams work for me.  It’s easy to write fiction because the characters don’t actually have to accomplish anything.  You can just write up a bunch of cool scenes and you’re done.  Can I learn anything from fiction?  Yes.  But generally, non-fiction is the most inspiring to me.

8. The Apollo 11 team:
Now here’s a real super hero team!  These guys went to the moon with less computing power then an iPod.  Pretty amazing when you think about it!

9. The Not Ready for Primetime Players:
Wonderful team of comedians!  I’ve always enjoyed them.

10. The Manhattan Project:
Yes!  Another great team of scientists that I can get behind.  Most people don’t know how great these guys actually were, and how they literally saved the world.  But sadly… most people don’t know history.

If I had created the list, I would have dropped the fictional teams.  Sure, they sound great, but it’s debatable how much they actually inspire.  For instance, Sherlock Holmes was a pretty smart character, but most people find it difficult to pattern their lives after a character in a novel.  It’s like trying to be more like Huck Finn or Indiana Jones.  It’s entertaining, but not inspiring.

Lastly, I would have liked to see “The 12 Disciples” listed as a team.  Jesus didn’t pick them for their skills and awesome speaking abilities, but in the end they changed the world.  That kind of power can’t be ignored, and they are men you can comfortably pattern your life after.

Overall… it was a fun article.  It was well thought out, and fun to read.

Posted on

The Harmonious Project Management Trinity

Regardless of the role you play in company projects, you will likely see three primary personalities in the project management and executive teams.  In other words, if you are involved in engineering a product, or managing the development of a new product or service, holding the executive reins of a company with project management, you will likely see individuals with the following three personality drives.  These three primary issues drive their thinking.

1. The “On Time” Person
The time conscience “On Time” person primarily worries about project schedules.  When will each subsystem be finished?  Each milestone?  Each Phase?  And when will the project ship?  This person studies and observes all the team interaction with dates and times in mind.  Is the project going to be late?  If so, what can we do to fix that?  His first suggestions are to defer features for a later release, cut the scope to something more manageable, and to create a smaller, foundational release that can be improved upon later.  In other words, meet the agreed-upon ship dates at all cost, and defer more advanced things until later.

2. The “On Budget” Person
The cost conscience “On Budget” person thinks much like the On Timer.  He thinks primarily about project costs.  Blow the budget by a dollar, and he freaks out!  And since the biggest cost in most project is human resources and salaries, he’s thinking the same thing as the time conscience person, “get the project done on time so you don’t blow my budget.  And if you don’t think you can get it done on time, cut something so my budget isn’t wrecked.”  Time and budget go closely hand in hand.

3. The “Quality” Person
The quality conscience person primarily thinks about the consequences of releasing a bad product.  What will the marketplace say?  How will customers receive it?  And the Press?  It’s hard to recover from bad press or a mainstream revolt against your product.  You could lose millions of dollars just from a Facebook uprising.  It would be far better to spend an extra month getting right, or an extra $100K, than to suffer a marketplace meltdown.

So you see that these personalities can be in conflict from time to time – not exactly harmonious at all times.  The Quality person doesn’t want to witness a total user-base revolt because of a poor product.  The budget person doesn’t want to sink the company in debt.  And the schedule person doesn’t want customers to walk away all because the product took too long to deliver.

The best hope a company has is to recognize that these personalities can all exist in one project management team.  Recognizing each one for its merits goes a long way.  Sometimes people just want their input valued.  The next step is to work together toward mutually agreeable compromise that includes input from each driving force.  Hopefully, the result is a good quality product that doesn’t ruin the company in debt and unresponsiveness.

Posted on

Taking Baby Steps

I ran across a nice video of how to take baby steps to implementing time tracking within your organization.  It’s worth watching.  Follow the link below for the video.

The theory is that you can get immediate value from a time tracking product like Standard Time® with minimal input.  And then after implementing the product, you can take several baby steps to gaining incremental value.  It’s up to you when you reach the point of diminishing returns (when more employee participation yields less value).  But this program has enough upward latitude to allow you to explore the upper limits of your company’s needs.

Follow the steps and see what you think!

Baby Steps For Time Tracking