What Are Stated Objectives?

Requirements: No different than purchasing equipment, make sure the objectives of a project are acquired by collecting and documenting requirements.

"What Do You Want?"
When I was about 8, I sat on Santa's lap and asked for a "Barbie Dream House." I imagined how wonderful that would be. Instead I got a knock-off Barbie Doll. So I used shoe boxes and washcloths for her house. The "house" was easy to build, flexible, economical, environmentally friendly, and most importantly met her (and Ken's!) needs.  Project requirements often describe the Dream House, so it will be important to categorize requirements, as it is unlikely the Dream House will be built to complete satisfaction or will even be needed.

Gathering and Organizing Requirements
There is plenty of debate on the best way to manage and deliver against requirements. The Practical Project Manager focuses on selecting tools and methodologies depending on the size and complexity of the project. 

Check out this concise summary on requirements analysis. 


When gathering requirements, make sure to rate each requirement for its importance and urgency in achieving the stated objective. Create a measurable way to determine what "finished" looks like. 

A simple spreadsheet that states  the category, requirement description, who requested it, what function it satisfies, its priority, urgency, and dependency may be all that is needed. 

For complex, large-scale projects, more sophisticated methods and tools may be required.  Look for tools that tie requirements, product development, testing, defects and changes, and user acceptance. 


Establish a traceability process, so a requirement can be traced through product development, testing, defects and changes, to user acceptance:


Ensure the right people are engaged. The people defining requirements and approving them may be two different teams.

Ensure requirements and decisions tie to overall project objectives, funding, and timeline.

Prioritize requirements: A) must have B) meets objectives C) rounds out delivery

Determine urgency: 1) must do now 2) can wait

Requirements have a priority/urgency rating: e.g. "A1" is a must have/urgent rating.



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

2 comments:

How To Actually Get Work Done, Action Items

What Is An Action Item?
A generally accepted definition is this:  "An action item is a documented activity, event, or task. Action items are discrete entities that can be dealt with by a single person."   While this is true, the Practical Project Manager knows action items are an important part of actually getting work done.  Successful projects have solid practices and controls around definining, managing and actually completing work associated with action items.


Action items are:  
  • Unplanned work associated with issue and risk management
  • Often discovered during a meeting or formal discussion regarding an issue or risk
  • Prioritized, assigned, managed for completion
Action items can sometimes be confused with unplanned work, that is, work that should have been documented as a task in the Project Schedule.  If there is significant unplanned work, the project may require a Scope Change.  

It is important to monitor action items to make sure there is not "Scope Creep".  Sometimes action items take on a life of their own, resulting in a significant work effort just to manage actions.  This can be an indicator that scope was not sufficiently managed or that additional scope is creeping into the project under the guise of action items.

How to Manage Action Items
The best way to manage action items is to record them in an ACTION ITEM LOG using a collaborative tool such as SharePoint or Google Apps.

Build a collaborative ACTION ITEM LOG that has the following features and includes email alerts to the responsible person, attachments, and a historical archive:
  • Description - Short explanation of activity to be performed
  • Work Stream - your project is probably organized into various work streams such as business requirements, technical design, user interface, etc. 
  • Issue or Risk - is this action item associated with a project issue or risk
  • Status - Open, In Progress, Resolved, Canceled, Transfered to Training Log
  • Urgency - how quickly does this action need to be performed?  1) must do now 2) can wait 
  • Priority - what is the impact to your project's critical path? 1) High 2) Medium 3) Low
  • Comments - 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?
  • Planned Completion Date - When will this issue be solved?
  • Actual Completion Date - Date issue was closed
The Practical Project Manager maintains the ACTION ITEM LOG and builds an interactive tool so actions can be maintained by those responsible for resolution.  Managing the team's work against completing the action items is the project manager's responsibility. 
Always refer to your company's methodology or the Project Management Institute for specific how-to.

1 comment:
Subscribe to: Posts (Atom)