Technical and Programmatic Controls

Technical and Programmatic Controls

Is there a credible activity network supported by a Work Breakdown Structure?

  • Have you identified your critical path items?
  • Is any work performed off the WBS, in a Control Account, or has a Work Package?
  • Does the activity network clearly organize, define, and graphically display the work to be accomplished?
  • Does the Top–level activity network graphically define the project from start to finish, including all the dependencies?
  • Does the lowest–level WBS show the Work Package's measurable tasks and duration?
  • Does each activity on the network have a well–defined deliverable, a measure of completion, or a stated outcome?
  • Is each Work Package or task set under budget control, expressed in labor hours, dollars, or other numerical units?

Is there a current, credible schedule and budget?

  • Is the schedule based on a project/activity network supported with a WBS?
  • Is the schedule based on realistic, historical, and quantitative performance estimates?
  • Does the schedule provide time for holidays, vacations, sick days, etc.?
  • Does the schedule shows all the necessary quality assurance activities?
  • Does the schedule account for resource overlaps?
  • Is the next three to six months' schedule as detailed as possible?
  • Is the schedule consistently updated at all levels in the Gantt, PERT, and Critical Paths views?
  • Can you perform to the schedule and budget?

What deliverables are being produced?

  • Are the program's operational requirements, outcomes, and deliverables clearly specified?
  • Are definitions of what the products or services must do to support the program capabilities clearly specified?
  • Do you know if the program interfaces with suppliers and sourced materials are specified and, if appropriate, prototyped?
  • Are descriptions of the technical environment and relationships of technical processes clearly specified?
  • Do you happen to know if specific development requirements are explicitly defined?
  • Do you know if specific acceptance and delivery requirements are explicitly defined?
  • Are customer requirements agreed to by joint teams of producers and consumers of the products, services, or capabilities?
  • Are all requirements traceable to each Work Package, Control Account, and deliverable?

Is there a list of the current Top Ten project risks?

  • Has a Risk Management role been assigned to the project?
  • Are risks determined through established risk identification, assessment, and mitigation processes?
  • Is there a database that includes all non–negligible risks in terms of probability, earliest expected visible symptom, estimated and actual schedule, and cost effects?
  • Are all project personnel encouraged to become risk identifiers?
  • Do you know if the database of Top Ten risks is updated regularly?
  • Are user requirements reasonably stable?
  • Do you know how the risks are changing over time?

What is the schedule compression percentage?

  • Has the schedule been constructed bottom-up from quantitative estimates rather than predetermined dates?
  • Has the schedule been updated when major modifications in the requirements have taken place?
  • Have technical and programmatic controls received training in the tools and processes needed to manage the program?
  • Does the project avoid extreme dependencies on specific individuals?
  • Are people working abnormal hours?
  • Do you know the historical schedule compression percentage on similar projects and the results of those projects?
  • Is any part of the schedule compression based on new technologies?
  • Has the percentage of program functionality been decreased in proportion to the percentage of schedule compression?

What is the estimated size of your deliverables in cost and work effort?

  • Do you know if the project scope has been established?
  • Were measurements from the previous projects used as a basis for size estimates?
  • Is the Basis of?Estimate been calibrated
  • Are the technical and programmatic staff estimating experience in the domain area?
  • Are estimates regularly updated to reflect technical realities?

What percentage of external interfaces are not under control?

  • Has each external interface been identified?
  • Have critical dependencies of each external interface been documented?
  • Has each external interface been ranked based on potential project impact?
  • Have procedures been established to monitor external interfaces until the risk is eliminated or substantially reduced?
  • Have agreements with the external interface controlling organizations been reached and documented?

Does the staff have enough expertise in the project domain?

  • Do you know what the user needs, wants, and expects?
  • Do you know if the staffing plan includes a list of the key expertise areas and the estimated personnel needed?
  • Do most of the project staff have experience with the specific type of product or service being developed?
  • Do most project staff have extensive experience in the tools and processes?
  • Could you let me know if the technical and programmatic staff can proceed without undue request for additional time and cost to help resolve technical problems?
  • Does the technical and programmatic staff understand their project role, and are they committed to its success?
  • Is there a domain area expert assigned to each domain?

Is there identified adequate staff for the scheduled tasks at the right time?

  • Do you have enough staff to support the tasks identified in the activity network?
  • Is the staffing plan based on historical data on the level of effort to staff months for similar projects?
  • Do you have adequate staffing for the current and scheduled tasks in the next two months?
  • Have alternative staff buildup approaches been planned?
  • Does the staff buildup rate match the rate at which the project leaders identify unsolved problems?
  • Is there sufficient range and coverage of skills on the project?
  • Is adequate time allocated for staff vacations, sick leave, training, and education?
  • Are staffing plans regularly updated to reflect reality?

Jan van den Berg

Author "Primavera P6 Practical Scheduling & Planning & Master Primavera P6" | Project Scheduling & Planning Expert

2 年

Glenn, thanks for your sharing your valuable knowledge on project management. I have read most of your articles and I note that this article sums up the vast oceans of knowledge in your crayon pencil.

回复

要查看或添加评论,请登录

Glen Alleman MSSM的更多文章

  • 2 - Fundamentals of Digital Engineering Systems

    2 - Fundamentals of Digital Engineering Systems

    This is the 2nd in a 3-part series on Digital Engineering. The 1st introduced the Capabilities of Digital Engineering.

  • Some GovLoop Publications

    Some GovLoop Publications

    GovLoop is The Knowledge Network for the Government of more than 300,000 federal, state, and local government peers in…

  • Five Immutable Principles of Project Success No Matter the Domain, Context, Management Tools, or Processes

    Five Immutable Principles of Project Success No Matter the Domain, Context, Management Tools, or Processes

    Here is a collection of materials I use to guide project success when we are not immune to common reasons for project…

    6 条评论
  • Planning is Everything

    Planning is Everything

    Plans are nothing; Planning is Everything. The notion that plans are nothing but planning is everything is a standard…

    3 条评论
  • Learning from Mistakes is Overrated

    Learning from Mistakes is Overrated

    We've all heard this before: hire good people and let them learn from their mistakes. The first question is, who pays…

    2 条评论
  • Quote of the Day

    Quote of the Day

    “The first rule of any technology used in a business is that automation applied to an efficient operation will magnify…

    3 条评论
  • Quote of the Day

    Quote of the Day

    For the sake of persons of different types, scientific truth should be presented in different forms and should be…

    1 条评论
  • The Fallacy of the Iron Tiangle

    The Fallacy of the Iron Tiangle

    The classic Iron Triangle of lore - Cost, Schedule, and Quality- has to go. The House Armed Services Committee (HASC)…

    9 条评论
  • Why Projects Fail - The Real Reason

    Why Projects Fail - The Real Reason

    At the Earned Value Analysis 2 Conference in November of 2010, many good presentations were given on applying Earned…

    2 条评论
  • Quote of the Day - Risk

    Quote of the Day - Risk

    The real trouble with this world of ours is not that it is an unreasonable world, nor even that it is a reasonable one.…

    6 条评论

社区洞察

其他会员也浏览了