• Topics

  • Log In

Thanks for Coming But…

We’re glad you’re here but everyone’s packed up and left town. Please visit us at our new location at

http://www.projectsolversofamerica.com/blog .

Pictures from 11-11-11 AM/PM Workshop

Here are the pictures from the AM/PM workshop held on 11/11/11 at Medialle College.

A Checklist for Determining Requirements

There are numerous stories and articles written on projects that failed because all the requirements were not defined or determined. Project success depends on full disclosure of requirements and that signing off of the requirements by the sponsor, stakeholders and the team. Requirements are the ―contract‖ with all those involved with the project and it must go hand in hand with a change control system and risk analysis.

Here is a quick checklist PMs‘ can use in determining the requirements for a project. This is by no means all inclusive but it gives you a good start in making sure you cover all of the bases.

  • Scope is a part of requirements – if the scope is not defined how you can determine the requirements?
  • Functional and Data requirements
  • Look, Feel and Use of the product – how easy will it be to use
  • Performance-speed, safety, reliability, availability
  • Operational requirements – supportability, maintainability, etc
  • Security – confidentiality, data integrity, audit
  • Legal-Are there governmental requirements, copyrights, patents
  • Standards of the industry or business
  • Off-the-shelf solutions – software that is ready to go or components in place
  • Solution constraints, external factors
  • Future-Is there a phase 2? Will company growth affect the requirements.

Use these eleven (11) items as a starting point for focusing your team in determining how you will collect and verify at least these critical requirements.

 

Defining the Work Package

A question I often hear is “what is the maximum time I should allocate to a task”?

First we need to define a “work package”. It is the act of breaking down deliverables in to successively smaller chunks of work to be completed in order to achieve a level of work that can be both realistically managed by the project manager and completed within a given time frame by one or more team members. Work packages are the lowest level of the WBS and are pieces of work that are specifically assigned to one person or one team of people to be completed. This is also the level at which the project manager has to closely monitor all project work.

Most project managers concur that this varies by project, but can usually be measured using the 8/80 Rule. The 8/80 Rule says that no work package should be less than 8 hours or greater than 80 hours.

A work package at the activity level is a task that:

  • can be realistically and confidently estimated;
  • makes no sense practically to break down any further;
  • can be completed in accordance with one of the heuristics defined above;
  • produces a deliverable which is measurable; and
  • forms a unique package of work which can be outsourced or contracted out

One more point to remember is to develop the project budget first before deciding on the ele-ments for the WBS. Without the money there is no project. The “BUDGET” has to consider the tasks in general and the materials, resources and even the estimated time to accomplish the project. Take the time to plan the budget, remember your tasks should follow the 8/80 rules and your project schedule should then be on sound footing.

Decision-Making Test

Since our theme this month centers on decision-making I thought you might be interested in reading this question and answer and taking the associated test. It was published by the IMC (Institute of Management Consultants). Will post the answers on Monday (no cheating!)

****

After nearly thirty years of management consulting, I consider myself to have good perception about client issues and to be an excellent decision maker. When is it OK to trust my instincts and when should I turn to others for verification?

Asking means you are aware that you might not be as good a decision maker as your experience might indicate. In fact, many of us overestimate our perceptiveness or decision making accuracy. Think you are a good decision maker? Let’s see.

Answer the following ten questions with a numerical range (one low and one high number) that you are 90% confident contains the correct answer (i.e., there is at most a 1 in 10 chance your range is too small). Next Monday we’ll provide the answers so you can see whether your decision making confidence is warranted.
1. Length of the Nile River (in miles)
2. Diameter of the moon (in miles)
3. Weight of an empty Airbus 380 (in pounds)
4. Year in which Wolfgang Amadeus Mozart was born
5. Gestation period of an Asian elephant (in days)
6. Air distance from Chicago to Shanghai (in miles)
7. Year the first spacecraft landed on the moon
8. Area of US national parks (in square miles)
9. Year in which Attila the Hun died
10. Average population density of the US (in people/sq mi)
Print out this tip and next to each numbered item write a lower and upper bound estimate (no Googling the answers!). Check back Monday.
________________________________________
Copyright (c) 2010, Institute of Management Consultants USA
Get your own subscription to Tip of the Day by email or by RSS feed Use the Update Profile link below to pick daily or weekly (Friday) delivery.

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: