How To Actually Get Work Done, Introduction

The Heartbeat of a Project is in Actually Getting Work Done


Actually "getting work done" can be extremely difficult if a project is bogged down by politics, bureaucracy, poor planning, a shortage of resources, or other external factors.


The Practical Project Manager actually gets work done by ensuring execution of day-to-day work activities, both Planned and Unplanned Work, with clear communication, deliberation, and enthusiasm.
  • Planned Work is documented in a Project Schedule (for example using Microsoft Project).  When work is planned, it is then "baselined", and provides the initial Estimate At Completion (EAC).  
  • Unplanned Work comes in two forms:

  1. action items associated with issue and risk management
  2. tasks that probably should be in the Project Schedule, that is, work that is required, but not previously planned.  

If Unplanned Work is significant, it may require a Plan Change, which would require an Updated Baseline and will provide a new Estimate at Completion (EAC).





Planned Tasks:  Project Scope is broken down into discrete work streams and work elements using a work breakdown structure (WBS) method.  These planned tasks include no more and no less than the work effort required to meet Project Scope.
Project Schedule:  a collection of tasks that include resources, start and end dates, dependencies, level of effort, and percentage of work completed for each activity.  There are many methodologies and software packages to create and maintain the schedule.  Typically the graphical representation of the schedule is a GANTT CHART.
Plan Baseline: once a project schedule is completed and approved it is said to be "baselined":  an agreed-upon plan for completing work.  With this original plan, performance of actual work can be compared to baseline as data points for  Earned Value Management and to provide better estimates for future projects.
Estimate at Completion (EAC):  If you plan the work, work the plan, and maintain status of work completed in the project schedule, you will always know total project cost and timeline.  EAC is a critical project metric and is determined by adding the actual cost of work performed (ACWP) plus the estimate to complete (ETC) for remaining work. 
Unplanned Tasks:  some work cannot be foreseen, however the Practical Project Manager knows work will arise from Action Items and Additional Tasks and provides enough "head room" in the plan for this inevitable work.
Plan Change:  the plan may need to change if work required is greater than expected, if there is a resource constraint, or there is an external force that causes and impact to the project.  A governance process should be in place to control changes to the plan.
Updated Baseline: upon approval of plan changes, the project schedule is updated and re-baselined.  

Updated Estimate at Completion (EAC): The new EAC is communicated and work commences against this new plan.






Always refer to your company's methodology or the Project Management Institute for specific how-to.



Risk and Issue Management

Managing Project Risks and Issues
I was on a project once where the sponsor said "we don't have any risks, but we have a lot of issues".   Hmmmm.....before those issues became issues, there must have been a RISK that they could occur.


The Practical Project Manager establishes tools, communication, and responsibilities for managing risks and issues.  Start by determining if the company has a project risk and issue management process in place.  If so, follow that process and be sure the following features are in place at the project level.




All projects automatically come with several risks and issues even before they start!

You may want to consider the major areas a project covers.  For example its requirements, timeline, budget all have inherent risks.  How this project interacts with other areas and initiatives, your resources and team, quality assurance, how teams and people communicate with one another, and how you are going to acquire resources to get the work done all come with inherent risks.  Even managing risks and issues has its risk!

If you follow the PMBOK® Knowledge Areas, you may want to consider aligning your risks and issues with their knowledge areas.  Please note: PMBOK® is a registered trademark of the Project Management Institute and is referenced here in the spirit of education and open content.
  • Integration
  • Scope
  • Time
  • Cost
  • Quality
  • Human Resources
  • Communication
  • Risks and Issues
  • Procurement

Risks
What is a Risk? "Could my project fail?"
Something that will impact overall success of the project.

Risks need to be weighted for their impact and probability, managed at the steering committee level, and have a clear escalation plan for resolution.

Each risk is documented as follows.  A simple spreadsheet is all that is needed to document risks.  List each risk in the left margin, add the following column headings, and sort the log by SCORE as described below.  Work on the largest risks first.

  • Description - a risk area may have more than one risk, for example there may be three integration risks
  • Probability - the chance this risk will actually occur (on a scale of 1-5, where 1 is not likely, and 5 is imminent)
  • Impact - the effect on your project (on a scale of 1-5, where 1 is very low, and 5 is catastrophic)
  • Score - determines the size of the risk and which risks require the most attention.  Multiply Probability X Impact.  An imminent, catastrophic risk has a score of 25.
  • Mitigation Plan - A description of what is now being done to avoid this risk from impacting your project
  • Contingency Plan - A description of what will be done if this risk actually causes an issue or potential project failure
  • Responsibility - Who is responsible for actively working the mitigation of this risk?
  • Next Step - What is the next activity for mitigating this risk?
  • Next Step Due Date - When is this person's next mitigation action due?

The Practical Project Manager maintains the PROJECT RISK LOG, reviews it with the Project Steering Team at least monthly, and gets status updates on next steps from responsible team members on a weekly basis.

Issues
What is an Issue?  "Do I need a course correction?"

Something that could slip a critical path in the project, but not yet likely to impact its overall success.
 
Issues are managed by the project manager at the team level and are prioritized with accountability and due dates.
 
All projects have issues, the larger the project, the larger the issues.  Issues tend to take on a life-form of their own, so keep a historical record of activity associated with an issue, especially decisions made along the way to resolve the issue.  As a reminder an issue is only an issue if it could slip a critical path in the project.  A difficult action or work activity is not necessarily an issue.
 
If you have access to a tool such as SharePoint or Google Apps, build collaborative ISSUE LOG that has the following features and includes email alerts to the responsible person, attachments, and a historical archive:

  • Description - a issue area may have more than one issue, for example there may be three quality issues
  • Work Stream - your project is probably organized into various work streams such as business requirements, technical design, user interface, etc. 
  • Status - Open, In Progress, Resolved, Canceled, Transfered to Training Log
  • Urgency - how quickly does this issue need to be resolved?  1) must do now 2) can wait 
  • Priority - what is the impact to your project's critical path? 1) High 2) Medium 3) Low
  • Resolution Plan - A description of what is now being done to solve the issue
  • Responsibility - Who is responsible for actively working the issue?
  • Created Date - Date issue was opened
  • Next Step - What is the next activity for working the issue?
  • Next Step Due Date - When is this person's next action due?
  • Expected Resolution Date - When will this issue be solved?
  • Resolution - A description of what was done to actually resolve the issue once it is closed
  • Resolution Date - Date issue was closed

The Practical Project Manager maintains the ISSUE LOG and builds an interactive tool so issue status can be maintained by those responsible for resolution.  However creation and setting the urgency and priority of an issue is the project manager's responsibility. 

Summarize issues with the Project Steering Team at least monthly and review issues with team leads on a weekly basis.  Build a summary report that includes the following:

  • Number of issues by work stream, urgency, and priority
  • Number of issues by person responsible
  • Average number of days to close an issue
  • Trend or graph issue management over time.  This is an excellent metric to tell a story such as "We had 25 issues last month with an average days open of 10.  However this month we have 35 issues and our average days open has increased to 15."

Remember that an Action is not an Issue or Risk, but rather a task that needs to be worked. Actions have resources, due dates, durations, and dependencies.


Always refer to your company's methodology or the Project Management Institute for specific how-to.


The Three-Legged Stool

Time, Cost, Quality: The Project Manager's Three-Legged Stool 

There are many analogies for "the three-legged stool", ours is all about balancing the budget with the timeline and the quality (which is usually measured by scope and thoroughness of products or services provided by the project).





"Absolutely Nothing Works!"

Yep, that was the primary complaint by one of my business owner on a large scale ERP project.  Hmmm.  Do we need to get more money to make sure we fix everything?  Do we need to push out our deadline?  Is our test plan so bad that we let a lousy solution move forward?  The impulse is to increase quality/scope, ask for more money, ask to extend the deadline to satisfy the business owner's complaint.    


The Practical Project Manager balances the three-legged stool by making course corrections.  This is done by maintaining great relationships and keeping communication flowing to ensure the best quality product or service is being produced.  Here is how:


Review your EXTERNAL FORCES CHECKLIST.   
  • What resources (time/cost/quality) are MOST available?  
  • Is your timeline more negotiable than your budget?  
  • Do you have a resource constraint or are there available resources who can help out?
  • Does your solution fit in with appropriate innovation or technology trends?  Is it off-point?
  • Does your solution meet the stated objectives, realizing there may be some kinks to work out?
  • Review which requirements are working / not working and how important they are to meeting your stated objective
Knowing what resources you can leverage is key, but first a little reality check on how things really work:

Constraints are set by external forces, specifically timeline and budget.  External forces also determine the value your project brings to the overall enterprise.  However, this may not be as apparent or important as the forces on  your timeline and budget.  Your Subject Matter Experts (or SMEs, pronounced "smeez") provide detailed requirements which guide your quality and scope.  


Here is the reality:  you will have a downward force to reduce the timeline and or budget, but will have upward force to increase the quality of your product or service to meet the stated objectives.  So most of your time will be spent ensuring the best quality work product is being produced within these constraints.

  • Talk to people one on one.  How are things actually going?  Are there actions, issues, risks that require attention or course correction?
  • Plan the work, work the plan.  Are you executing against plan?
  • What is your ETC (Estimate To Complete)?  Do you know at all times what percent of work is complete and what percent is remaining to meet stated objectives?
  • Conduct a DAILY STAND UP with your team (or request your team leads do this with their respective teams)
  • Conduct a PROJECT REVIEW with team leads every week
  • Update your plan and calculate your ETC (ESTIMATE TO COMPLETE) once a week
  • Report written status to the PROJECT SPONSOR at least every two weeks
  • When writing status reports, make sure to get feedback and approval for course correction; your status includes where you are at COMPARED TO WHERE YOU PLANNED TO BE AT.
  • Document COURSE CORRECTION decisions
  • BALANCE THE BUDGET once a month




Always refer to your company's methodology or the Project Management Institute for specific how-to.

Announcing my new blog on Solution Leadership, "The Solutionist"

Follow me at http://solutionleadership.blogspot.com/  If you are an aspiring solution architect or IT manager, take a look at this digest on how to design and lead solutions. 


As many of you know I am organizing and posting my professional notes in three topics.  Two down, one to go!

The Practical Project Manager
New!  The Solutionist
Coming Soon!  The 360.CIO

Enjoy!  Your feedback is appreciated.