You are here: Home Blogs Displaying items by tag: deliverable
Project Management Blog
We’ve beaten Mr. Genius, Ms. Bellows, Mr. Promise and Mrs. Process.  But what chance do we have against Ms. Meetings?  She is very sweet.  As a matter of fact, she brings donuts to all of her meetings.  And she certainly has a lot of them.  Any time there is a question she calls a meeting.  She has regularly scheduled Status Meetings, Team Meetings, Progress Meetings and Recap meetings.  During testing there is a meeting at 7:00 AM to determine the daily schedule, a meeting at noon to check on status and one at 6:00 PM to review results.  Then every hour on the hour she meets with the individual areas to make sure progress is being made.  She even had a couple of meeting to determine why productivity was so low.
Published in Blogs
Thursday, 17 May 2007 15:32

Deming's 4th Point in Project Management

Consider Costs and Benefits of the Entire System and Deliverable Lifetime

The textbook wording of this point varies, but is usually something like “Stop making decisions purely on the basis of cost.” When I read the various descriptions however, I believe the textbook title is not an adequate summary.

When Deming talks about not making decisions purely on the basis of cost, he is referring to a plant perspective and talks about the importance of having regular suppliers.

Published in Blogs
Friday, 13 April 2007 12:06

It Was An Itsy Bitsy, Teeny Weeny......

Finding the right balance of documentation and methodology can be challenging on small projects.  Here are some tips. 

I have been managing small projects for some time now.  Some of my project are really tiny, I'm talking about 8 hours of work max.  Others can be 2 week or month-long projects.  Some span several months, and then you get up into the 6 month and year plus undertakings.

Published in Blogs
Monday, 09 April 2007 08:24

Audit Failures

I have a friend who used to work for the Internal Revenue Service (IRS) as a tax collector for the United States.  When he performed an audit he expected you to be honest and work with him to determine what was owed.  He had the authority to make your life miserable if you chose to mess around.  After trying unsuccessfully on one case to work through issues with an individual he showed up at the company before 6:00 AM with padlocks and chains to impound all of the vehicles.  In concert with this move he froze all financial assets as soon as the bank opened. 
Published in Blogs
Sunday, 18 February 2007 19:31

9 Benefits of a Project Schedule

The Value of a Project Schedule: "Failing to plan means planning to fail".In my mind, that sums it up.  But this article will focus on providing some more detailed benefits.Contrary to what you might be thinking, this article is NOT some type of promotion for the use of Microsoft Project.  As a matter of fact, your schedule could be developed on a napkin, providing you (and your team) develop it, and manage with it!!
Published in Blogs
Thursday, 25 January 2007 17:41

Configuration Management

Configuration management is the term given to the identification, tracking and managing of all the assets of a project; it focuses on controlling the characteristics of a product or service (also referred to as deliverables). In a general sense, configuration management consists of the following:

 

  • The documentation of the features, characteristics, and functions of a product or service
  • The applied control to restrict changes to the features, characteristics, and function of the product or service
  • The process of documenting any changes to the product or service
  • The ongoing auditing of products and services to ensure their conformance to documented requirements
  • Establishes a method to consistently identify and request changes to established baselines
  • To assess the value and effectiveness of changes
  • Provides opportunities to continuously validate and improve the project by considering the impact of each change
  • Provides the mechanism for the project management team to consistently communicate all changes to the stakeholders.

 

Configuration management activities included in the integrated change control process are:

  • Configuration Identification - Providing the basis from which the configuration of products is defined and verified, products and documents are labeled, changes are managed, and accountability is maintained.
  • Configuration Status Accounting - Capturing, storing, and accessing configuration information needed to manage products and product information effectively.
  • Configuration Verification and Auditing - Establishing that the performance and functional requirements defined in the configuration documentation have been met.

When it comes to configuration management, think paperwork. Think about all the paperwork that is involved in documenting every single component of a system deliverable and making sure that there are no changes to that deliverable, or if there are changes, that they are thoroughly documented. Configuration management is traceable. For the exam, know that all change must be screened, tracked, accepted, approved, and the development process updated thereafter.

 

Published in Blogs
Thursday, 25 January 2007 15:15

Stakeholder Management

You should recognize the importance of involving stakeholders in the development of the project plan. It is the responsibility of the project manager and the project team to create an environment in which all stakeholders can contribute as appropriate, but recognize that who contributes and the level of the contribution will vary by stakeholder. There are usually a number of people who are either directly involved in a project or who have a stake in its outcome. These people are called stakeholders. The key stakeholders in most projects are:

Published in Blogs
Page 1 of 2

News and Promotions

Keep up to date with the latest happenings by signing up for our newsletter. Subscribe below.

Twitter Update

Who's Online

We have 749 guests and no members online

Got something to say?