This document provides a project management plan for the [Project Name] Infrastructure Project from the present until the next major milestone. It outlines the purpose, definitions, governance structure, key roles, and higher level strategic requirements for the project. The project aims to [briefly state project objectives] and produce benefits such as [list 1-2 key benefits]. The project requires approval from the Project Customer and Sponsor before proceeding to the next stage of [Proposal/Options Analysis/Business Case/Project Plan]. The project will be managed according to the Transport and Main Roads project management methodology and portfolio/program requirements.
the lean procurement canvas and lean procurement are as disruptive for procurement, sales and partner management, as the business model canvas and lean startup where for business development
This presentation i had prepared for the workshop that i conducted for JP Morgan Employees. In the beginning it was rolled out to few employees & they rolled to people in management level too.
the lean procurement canvas and lean procurement are as disruptive for procurement, sales and partner management, as the business model canvas and lean startup where for business development
This presentation i had prepared for the workshop that i conducted for JP Morgan Employees. In the beginning it was rolled out to few employees & they rolled to people in management level too.
For numerous large enterprises, the alignment of hardware and software processes is critical to managing an Agile environment. Agile Hardware implementations can be put in place by using the same framework as our typical Agile Software Development transformations. Start off with assessing the organization’s current state, then move to planning and preparing by and putting together a transition backlog, start execution with training and coaching, spread the cultural shift with change management and maintain and scale the transformation.
It is a fallacy that the roles are Product Manager vs. Product Owner. Both can, and do, co-exist in an organization. This presentation explains the role of software product manager and agile product owner. Useful for people not familiar with these terms.
Business analyst interview questions and answersRobin G
Prepare better for your interview with this comprehensive set of 'Business Analyst Interview Questions and Answers'.
Courtesy : http://thebusinessanalystjobdescription.com
مراجعة ادارة المشتريات - جمعية المهندسين المصريين في الرياض
https://www.youtube.com/watch?v=-d48_IVpud4&index=5&list=PL9HqmhqTzU-UVL9Z2wGyzo8tALNOC2ym7
What is agile? Where did it come from, and how can it help me?
This session will go through a history of agile, including the origins of waterfall, the Toyota Production System and lean manufacturing, the creation of the agile manifesto, and how these all lead to the modern agile development frameworks we use today. By exploring the original design and intent behind agile principles and practices, we'll also uncover common pitfalls to agile adoption, and insights into overcoming them.
Use content-ready Procurement PowerPoint Presentation Slides to execute the process of acquiring goods and services from an external source via tendering. Meet customers & stakeholders demands, analyse processes, optimize strategies and ultimately reduce procurement costs. Incorporate professionally designed procurement PowerPoint PPT templates to transform your business which bring you benefits. This deck comprises of templates such as procurement strategy structure, procurement steps, procurement workflow process, procurement strategy, approach to procurement, formulating procurement strategy, creating procurement strategy, and more. Use this presentation for purchase planning, value analysis, financing, price negotiation, inventory control and stores, standards determination, etc. These procurement PowerPoint templates are completely customizable. Edit color, text, icon and font size as per your requirement. Add or remove content, if needed. Grab ready-to-use procurement PowerPoint complete presentation to go step by step process of acquiring goods and services from external suppliers. Good expression is guaranteed with our Procurement Powerpoint Presentation Slides. Communication becomes explicitly clear.
This project charter guide covers everything you need to know about the project charter. It is based on the free template you can download here: http://project-charter-template.casual.pm/
Business Case Pratictioners Forum: Business case - an overview, Stefan Sanchez, 22 April 2016
APM Benefits Management SIG
The APM Competence Framework describes the Business Case competence as “The ability to prepare, gain approval of, refine and update business cases that justify the initiation and/or continuation of change initiatives in terms of benefits, costs and risks.”
It further provides information regarding the application and knowledge such as; strategic arguments, options appraisal, benefits and dis-benefits, commercial aspects, risk, time scales and whole-life costs.
Those who work in the public sector will be familiar with the HM Treasury Green Book: appraisal and evaluation in central government and the Five Case model.
Business cases should be understood as both as a product and a process, with involvement from the right stakeholders in order to achieve the spending objectives and deliver benefits.
The inaugural Business Case Practitioners Forum (BCPF) brought together practitioners
-To share business-case related knowledge, experience and good practice drawn from the public, private and third sectors
-To support members to improve standards and consistency business cases
-To create a supportive and professional network of business case practitioners
-To develop a business case practitioner ‘body of knowledge’
Agile is a software development methodology in which the development is carried out iteratively and the requirements evolve through continuous inspection and adaptation. Some of the most commonly used agile software development methods/frameworks are: Adaptive Software Development (ASD), Extreme Programming (XP), Scrum and Kanban.
Product Backlog Refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. The Scrum Team decides how and when refinement is done. Refinement usually consumes no more than 10% of the capacity of the Development Team. However, Product Backlog items can be updated at any time by the Product Owner or at the Product Owner’s discretion.
Here is a presentation that I recently presented for an SAP Users Group. It provides a good overview of the concepts of Lean and Agile and the considerations for introducing Lean and Agile into an SAP or ERP project.
For numerous large enterprises, the alignment of hardware and software processes is critical to managing an Agile environment. Agile Hardware implementations can be put in place by using the same framework as our typical Agile Software Development transformations. Start off with assessing the organization’s current state, then move to planning and preparing by and putting together a transition backlog, start execution with training and coaching, spread the cultural shift with change management and maintain and scale the transformation.
It is a fallacy that the roles are Product Manager vs. Product Owner. Both can, and do, co-exist in an organization. This presentation explains the role of software product manager and agile product owner. Useful for people not familiar with these terms.
Business analyst interview questions and answersRobin G
Prepare better for your interview with this comprehensive set of 'Business Analyst Interview Questions and Answers'.
Courtesy : http://thebusinessanalystjobdescription.com
مراجعة ادارة المشتريات - جمعية المهندسين المصريين في الرياض
https://www.youtube.com/watch?v=-d48_IVpud4&index=5&list=PL9HqmhqTzU-UVL9Z2wGyzo8tALNOC2ym7
What is agile? Where did it come from, and how can it help me?
This session will go through a history of agile, including the origins of waterfall, the Toyota Production System and lean manufacturing, the creation of the agile manifesto, and how these all lead to the modern agile development frameworks we use today. By exploring the original design and intent behind agile principles and practices, we'll also uncover common pitfalls to agile adoption, and insights into overcoming them.
Use content-ready Procurement PowerPoint Presentation Slides to execute the process of acquiring goods and services from an external source via tendering. Meet customers & stakeholders demands, analyse processes, optimize strategies and ultimately reduce procurement costs. Incorporate professionally designed procurement PowerPoint PPT templates to transform your business which bring you benefits. This deck comprises of templates such as procurement strategy structure, procurement steps, procurement workflow process, procurement strategy, approach to procurement, formulating procurement strategy, creating procurement strategy, and more. Use this presentation for purchase planning, value analysis, financing, price negotiation, inventory control and stores, standards determination, etc. These procurement PowerPoint templates are completely customizable. Edit color, text, icon and font size as per your requirement. Add or remove content, if needed. Grab ready-to-use procurement PowerPoint complete presentation to go step by step process of acquiring goods and services from external suppliers. Good expression is guaranteed with our Procurement Powerpoint Presentation Slides. Communication becomes explicitly clear.
This project charter guide covers everything you need to know about the project charter. It is based on the free template you can download here: http://project-charter-template.casual.pm/
Business Case Pratictioners Forum: Business case - an overview, Stefan Sanchez, 22 April 2016
APM Benefits Management SIG
The APM Competence Framework describes the Business Case competence as “The ability to prepare, gain approval of, refine and update business cases that justify the initiation and/or continuation of change initiatives in terms of benefits, costs and risks.”
It further provides information regarding the application and knowledge such as; strategic arguments, options appraisal, benefits and dis-benefits, commercial aspects, risk, time scales and whole-life costs.
Those who work in the public sector will be familiar with the HM Treasury Green Book: appraisal and evaluation in central government and the Five Case model.
Business cases should be understood as both as a product and a process, with involvement from the right stakeholders in order to achieve the spending objectives and deliver benefits.
The inaugural Business Case Practitioners Forum (BCPF) brought together practitioners
-To share business-case related knowledge, experience and good practice drawn from the public, private and third sectors
-To support members to improve standards and consistency business cases
-To create a supportive and professional network of business case practitioners
-To develop a business case practitioner ‘body of knowledge’
Agile is a software development methodology in which the development is carried out iteratively and the requirements evolve through continuous inspection and adaptation. Some of the most commonly used agile software development methods/frameworks are: Adaptive Software Development (ASD), Extreme Programming (XP), Scrum and Kanban.
Product Backlog Refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. The Scrum Team decides how and when refinement is done. Refinement usually consumes no more than 10% of the capacity of the Development Team. However, Product Backlog items can be updated at any time by the Product Owner or at the Product Owner’s discretion.
Here is a presentation that I recently presented for an SAP Users Group. It provides a good overview of the concepts of Lean and Agile and the considerations for introducing Lean and Agile into an SAP or ERP project.
A strategic approach to policy engagement for research organisationsJames Georgalakis
This is the presentation delivered as part of a two day workshop held in Nepal in 2014 aimed at communications professionals or the point person for communication within fifteen South Asian think tanks. Participants explored how they could adopt a systematic approach to planning research or knowledge outputs for policy engagement and influence. They explored the types of influencing outcomes they are focused on and their individual and institutional capacities to deliver strategic communication and policy engagement work. By the end of the workshop it was hoped that each participating institution would have identified a clear set of steps towards the development of a strategic approach to policy engagement and research communication at an institutional or programmatic level.
This workshop formed part of the IDRC funded Think Tanks Initiative South Asia programme. http://www.idrc.ca/EN/Programs/Social_and_Economic_Policy/Think_Tank_Initiative/Pages/About.aspx
A Project Feasibility Study for the Establishment of E&J FarmsJandel Gimeno
This is a feasibility study made and conducted by our group entitled "A Project Feasibility Study for the Establishment of E&J FARM in ALFONSO, CAVITE". The group was composed of Mr. Alvin Hermoso, Efren Paul Vicedo, Jandel Gimeno, Mary Grace Orpia, Diana Ruado, Kristine Mendoza and Analyn Odal. The said Project Study was submitted to the Faculty of Business Administration & Accountancy Department of the Rogationist College.
(It was so CHALLENGING FOR US, yet so Successful! : )
Structured Approach to Solution ArchitectureAlan McSweeney
The role of solution architecture is to identify answer to a business problem and set of solution options and their components. There will be many potential solutions to a problem with varying degrees of suitability to the underlying business need. Solution options are derived from a combination of Solution Architecture Dimensions/Views which describe characteristics, features, qualities, requirements and Solution Design Factors, Limitations And Boundaries which delineate limitations. Use of structured approach can assist with solution design to create consistency. The TOGAF approach to enterprise architecture can be adapted to perform some of the analysis and design for elements of Solution Architecture Dimensions/Views.
You need to create a formal document that can be used to guide project execution and control. Get this template @ http://www.demandmetric.com/content/project-plan-template
[Insert project title, e.g. Cosmo Inc.”] Project Scope State.docxgerardkortney
[Insert project title, e.g. “Cosmo Inc.”]: Project Scope Statement[Insert learner name]Capella UniversityProject Scope Statement
Note: Any work not explicitly included in the Project Scope Statement is implicitly excluded from the project.
Project Name
Prepared By
Date
(MM/DD/YYYY)Version History (insert rows as needed):VersionDateComments
1.0
1. Executive Summary
Provide below a brief overview of this project (for example, project purpose and justification).
Note: In any instance where there is a discrepancy between the Project Charter and the Project Scope Statement, the latter is considered authoritative.2. Business Objectives2.1 Product Description (
Solution
)
2.2 Business Objectives
3. Project Description
For each area below, provide sufficient detail to define this project adequately.3.1 Project Scope
Includes (list deliverables):
Does not include:
3.2 Dependencies (External and Internal)
3.3 Assumptions
3.4 Constraints
4. Project MilestonesTarget Date
Project Start
Project Complete
5. Project Approach
Briefly describe how each of the following will be handled. Provide links to relevant documents as appropriate. 5.1 Change Management
5.2 Communication Management
5.3 Quality Management
5.4 Resource Management
5.5 Critical Success Factors
5.6 Risk Management
5.7 Project Organization
6. AuthorizationsThe Project Scope Statement is approved by the:
Project Sponsor
Project Manager
Project performance baseline changes will be approved by the:
Project Sponsor
Project Manager
Project deliverables will be approved and accepted by the:
Project Sponsor
Key Stakeholders
7. Project Scope Statement ApprovalProject Name
Project Manager
The purpose of this document is to provide a vehicle for documenting the initial planning efforts for the project. It is used to reach a satisfactory level of mutual agreement between the Project Manager and the Project Sponsors and Owners with respect to the objectives and scope of the project before significant resources are committed and expenses incurred.
I have reviewed the information contained in this Project Scope Statement and agree:NameRoleSignatureDate
The signatures above indicate an understanding of the purpose and content of this document by those signing it. By signing this document, they agree to this as the formal Project Scope Statement document.
References
2
PM5018 Business Case
PM5018 Business CaseCosmo, Inc.
Cosmo, Inc. is a leader in the development and distribution of wearable technology, including fitness coaching, nutritional coaching, and lifestyle advising products. The company holds a 33-percent market share in the wearable technology category. After doing marketing analysis, senior leadership realizes the onset of competition could negatively impact future earnings.
CEO and President Harold Living tells his leadership Cosmo, Inc. needs a new marketing strategy to not only increase market share but to maintain current le.
MBA 6951, Managing Complex Projects 1 Course Learning.docxAASTHA76
MBA 6951, Managing Complex Projects 1
Course Learning Outcomes for Unit II
Upon completion of this unit, students should be able to:
1. Examine the roles and responsibilities of a project manager.
1.1 Explain a project proposal that includes the project scope, schedule, and ultimate deliverables
that will be executed by a project manager.
2. Analyze the elements of measures of performance in the context of the triple constraints.
2.1 Explain a project proposal that includes risks in the context of the triple constraints.
2.2 Explain a project proposal that includes deliverables through measures of performance.
3. Determine the scope of a project.
3.1 Determine a project proposal that provides an overview of the scope of a project.
Course/Unit
Learning Outcomes
Learning Activity
1.1
Unit Lesson
Chapter 5: Management Functions, pp. 145-170
Chapter 7: Conflicts, pp. 237-246
Unit II Assignment
2.1
Unit Lesson
Chapter 5: Management Functions, pp. 145-170
Chapter 7: Conflicts, pp. 237-246
Unit II Assignment
2.2
Unit Lesson
Chapter 5: Management Functions, pp. 145-170
Chapter 7: Conflicts, pp. 237-246
Unit II Assignment
3.1
Unit Lesson
Chapter 5: Management Functions, pp. 145-170
Unit II Assignment
Reading Assignment
Chapter 5: Management Functions, pp. 145–170
Chapter 7: Conflicts, pp. 237–246
Unit Lesson
Management responsibilities involve the planning, organizing, staffing, controlling, and directing of people and
activities that will ultimately achieve the objectives parlayed within the organizational goals. Controlling is
actually a measurement function, which allows for evaluation and ultimate corrections that lead to ongoing
improvement and innovation within the organization. Directing suggests that the leader is actually
implementing the plans and involves several steps.
The interactive slide below explains the different steps in directing by the leader:
Click here to access the interactive slide.
Click here to access the interactive slide transcript.
UNIT II STUDY GUIDE
Managing Projects
https://online.columbiasouthern.edu/bbcswebdav/xid-77177349_1
https://online.columbiasouthern.edu/bbcswebdav/xid-77175396_1
MBA 6951, Managing Complex Projects 2
UNIT x STUDY GUIDE
Title
Once this structure has been established, managers must journey through the concepts of power, authority,
and responsibility. The ideal situation is that a project manager would have both the responsibility and
authority to complete the task, but many times, they have the authority but not necessarily the formal power.
This creates a void in their effectiveness unless they can utilize other influences such as those indicated in
the interactive slide below.
The interactive slide below explains the different types of rewards and examples.
Click here to access the interactive slide.
Click here to access the interactive slide transcript.
Another important ar.
Project Management Plan Templatewww.ProjectManagementDocs.com.docxbriancrawford30935
Project Management Plan Template
www.ProjectManagementDocs.com
Project Management Plan Template
This Project Management Plan Template is free for you to copy and use on your project
and within your organization. We hope that you find this template useful and
welcome your comments. Public distribution of this document is only permitted
from the Project Management Docs official website at:
www.ProjectManagementDocs.com
Project Management Plan
<Project Name>
Company Name
Street Address
City, State Zip Code
Date
Table of Contents
2Introduction
2Project Management Approach
3Project Scope
3Milestone List
4Schedule Baseline and Work Breakdown Structure
4Change Management Plan
5Communications Management Plan
7Cost Management Plan
9Procurement Management Plan
9Project Scope Management Plan
10Schedule Management Plan
11Quality Management Plan
13Risk Management Plan
13Risk Register
13Staffing Management Plan
15Resource Calendar
15Cost Baseline
16Quality Baseline
17Sponsor Acceptance
Introduction
The Introduction provides a high level overview of the project and what is included in this Project Management Plan. This should include a high level description of the project and describe the projects deliverables and benefits. Excessive detail is not necessary in this section as the other sections of the project plan will include this information. This section should provide a summarized framework of the project and its purpose. Look back at the Project Charter for information to include in this section.Project Management Approach
This section is where you outline the overall management approach for the project. This section should describe, in general terms, the roles and authority of project team members. It should also include which organizations will provide resources for the project and any resource constraints or limitations. If there are any decisions which must be made by specific individuals—for example authorizing additional funding by the project sponsor—this should also be stated here. It should be written as an Executive Summary for the Project Management Plan.
State the scope of the project in this section. The scope statement from the project charter should be used as a starting point; however, the project plan needs to include a much more detailed scope than the charter. This detail should include what the project does and does not include. The more detail included in this section, the better the product. This will help to clarify what is included in the project and help to avoid any confusion from project team members and stakeholders. Milestone List
Provide a summary list of milestones including dates for each milestone. Include an introductory paragraph in this section which provides some insight to the major milestones. This section should also mention or discuss actions taken if any changes to the milestones or delivery dates are required.
Milestone
Description
Date
Complete Requirements Gather.
Assignment 1/AgileProjectCharterTemplateExample.pdf
C Example Project/Program Charter
Template
THIS APPENDIX CONTAINS AN EXAMPLE of a project charter template that can be used to define the
macro layer in a hybrid, managed agile development approach. This template is provided as an
example and is intended to be customized to fit the project and business environment that it is
used in.
Project overview
Background
Provide a brief description of the background behind the problem that the project or program is
intended to address to a sufficient level to allow the reader to understand the context of the problem.
Problem Statement
Provide a brief description of the problem that the project or program is intended to address from a
business or operational management perspective.
Project Vision
Write a concise vision statement that summarizes the purpose and intent of the project and describes
what the world will be like when the project is completed. The vision statement should reflect a bal-
anced view that will satisfy the needs of diverse customers as well as those of the developing organiza-
tion. It may be somewhat idealistic, but it should be grounded in the realities of existing or anticipated
387
388 E X A M P L E P R O J E C T / P R O G R A M C H A R T E R T E M P L AT E
customer markets, enterprise architectures, organizational strategic directions, and cost and resource
limitations. Consider using the following template:
◾ For (target customer)
◾ Who (statement of the need or opportunity)
◾ The (product name)
◾ Is a (product category)
◾ That (key benefit, compelling reason to buy or use)
Success Criteria
What are the success criteria for the project? How do you know if the project has been successful?
Project Approach/Development Process
Identify the development process and/or any deviations from the standard methodology that will be
used for this project or program.
Project plan
This section outlines the plan for managing the project.
Scope
The project scope defines the range of the proposed products and services the project will deliver.
Scope can be represented using a context diagram, an event list, and/or a feature table. Scope might
be subdivided into the scope of the initial product release and planned growth strategies for subse-
quent releases. It is also important to define what the project will not include, so describe limitations
and exclusions, such as product features or characteristics that a stakeholder might anticipate, but
which are not planned to be included in the project.
In Scope
The project scope provides an overview of the user stories that the project will deliver. Scope might be
subdivided into the scope of the initial product release and planned growth strategies for subsequent
releases.
Release Priority Story # Story Name Description
E X A M P L E P R O J E C T /P R O G R A M C H A R T E R T E M P L AT E 389
Out of Scope
It’s also important to define what the ...
PROJECT MANAGEMENT PLAN TEMPLATE This Project Mana.docxwkyra78
PROJECT MANAGEMENT PLAN TEMPLATE
This Project Management Plan Template is free for you to copy and use on your project
and within your organization. We hope that you find this template useful and
welcome your comments. Public distribution of this document is only permitted
from the Project Management Docs official website at:
www.ProjectManagementDocs.com
PROJECT MANAGEMENT PLAN
<PROJECT NAME>
COMPANY NAME
STREET ADDRESS
CITY, STATE ZIP CODE
DATE
http://www.projectmanagementdocs.com/�
Project Management Plan Template
www.ProjectManagementDocs.com
1
TABLE OF CONTENTS
INTRODUCTION ................................................................................................................................ 2
PROJECT MANAGEMENT APPROACH ................................................................................................ 2
PROJECT SCOPE ................................................................................................................................ 3
MILESTONE LIST .............................................................................................................................. 3
SCHEDULE BASELINE AND WORK BREAKDOWN STRUCTURE .......................................................... 4
CHANGE MANAGEMENT PLAN ......................................................................................................... 4
COMMUNICATIONS MANAGEMENT PLAN ......................................................................................... 5
COST MANAGEMENT PLAN .............................................................................................................. 7
PROCUREMENT MANAGEMENT PLAN ............................................................................................... 9
PROJECT SCOPE MANAGEMENT PLAN .............................................................................................. 9
SCHEDULE MANAGEMENT PLAN .................................................................................................... 10
QUALITY MANAGEMENT PLAN ...................................................................................................... 11
RISK MANAGEMENT PLAN ............................................................................................................. 13
RISK REGISTER .............................................................................................................................. 13
STAFFING MANAGEMENT PLAN ..................................................................................................... 13
RESOURCE CALENDAR ................................................................................................................... 15
COST BASELINE ............................................................................................................................. 15
QUALITY BASELINE ..................................................................................... ...
Customerlogo hereProject Name Project CharterCompanylogOllieShoresna
Customer
logo here
Project Name: Project Charter
Company
logo here
Project Name: Project Charter
The blue-colored text passages within this document are tips and guidance for filling out
this template. If you are ready with your first draft, you should delete these passages before sending the document to your sponsor.
Project:
Project Name
Title:
Project Charter
Document number:
Version
0.1
Document status:
Draft
Author:
Doe, John
Responsible:
Date created:
dd.mm.yy
Protection class:
"For internal use only"
The Project and Author fields are filled automatically with the data from the document properties (File Properties). Once the appropriate entries have been made here, these fields can be updated with the "Update Field" function (can be found in the context menu for the individual fields).
Possible states for the document status include "Draft," "Released," and "Final." The status of the current document should be specified respectively in the field above.
Document history
Version
Date
Author
Comment/Change
0.1
dd.mm.yy
Draft
The document history should provide an overview of the development of the document. Different versions with their date, author, and possible comments should be entered here.
Tips for Using This Template:
The Statement of Work (SOW) forms the basis for the project order. The project order represents a further level of detail. Information that is often only outlined roughly in the SOW has to be provided in greater detail in the project order. Furthermore, internal points can also often be listed in the project order, which are essential for project success.
The blue text contained in the template should provide assistance for usage. It briefly describes how the individual elements and styles are to be understood.
Please delete all of the blue text before you disseminate or print the document; it is intended exclusively for internal use.
Page
1Background/Project purpose or justification
2Goals
2.1Goals
2.2Scheduling goals/milestones
3Project product description
4Delivery units
4.1Delivery units/services
5Project success criteria
6High-level risks
7Key stakeholders
8Assumptions, restrictions and external dependencies
9Responsibility of the customer
9.1Tasks
9.2Resources and staffing
10Project category
11Project budget (overview)
12Project startup
13Project end
13.1Signatures for release
Annex
A.Glossary and abbreviations
B.References, accompanying documents
1
1. Background/Project Purpose or Justification
This section describes why the project was initiated and how significant it is for the company.
2 Goals
This section describes which goals are to be realized with the project. These goals serve as a point of reference for the project closing. Measurable goals should be defined.
2.1 Goals
Goal
Description
2.2 Scheduling Goals/Milestones
Schedule
Description
3 Project Product Description
This section describes the project end product to be supplied.
Prod ...
Project Management Plan TemplateThis Project Management Plan.docxwoodruffeloisa
Project Management Plan Template
This Project Management Plan Template is free for you to copy and use on your project
and within your organization. We hope that you find this template useful and
welcome your comments. Public distribution of this document is only permitted
from the Project Management Docs official website at:
ProjectManagementDocs.com
Project Management Plan
<Project Name>
Company Name
Street Address
City, State Zip Code
Date
Table of Contents
Introduction3
Project Management Approach3
Project Scope3
Milestone List3
Schedule Baseline and Work Breakdown Structure3
Change Management Plan4
Communications Management Plan4
Cost Management Plan5
Procurement Management Plan6
Project Scope Management Plan6
Schedule Management Plan7
Quality Management Plan7
Risk Management Plan7
Risk Register7
Staffing Management Plan8
Resource Calendar8
Cost Baseline8
Quality Baseline8
Sponsor Acceptance10
Introduction
The Introduction provides a high-level overview of the project and what is included in this Project Management Plan. This should include a high-level description of the project and describe the projects deliverables and benefits. Excessive detail is not necessary in this section as the other sections of the project plan will include this information. This section should provide a summarized framework of the project and its purpose. Look back at the Project Charter for information to include in this section.
Project Management Approach
This section is where you outline the overall management approach for the project. This section should describe, in general terms, the roles and authority of project team members. It should also include which organizations will provide resources for the project and any resource constraints or limitations. If there are any decisions which must be made by specific individuals—for example authorizing additional funding by the project sponsor—this should also be stated here. It should be written as an Executive Summary for the Project Management Plan.
Project Scope
State the scope of the project in this section. The scope statement from the project charter should be used as a starting point; however, the project plan needs to include a much more detailed scope than the charter. This detail should include what the project does and does not include. The more detail included in this section, the better the product. This will help to clarify what is included in the project and help to avoid any confusion from project team members and stakeholders.
Milestone List
Provide a summary list of milestones including dates for each milestone. Include an introductory paragraph in this section which provides some insight to the major milestones. This section should also mention or discuss actions taken if any changes to the milestones or delivery dates are required.
Schedule Baseline and Work Breakdown Structure
This section should discuss the WBS, WBS Dictionary, and Schedule baseline ...
Franchise Agreement Analysis Paper Guidelines and Grading Guide.docxMARRY7
Franchise Agreement Analysis Paper Guidelines and Grading Guide
Overview
In this project, you will develop a Franchise Agreement Critical Analysis, based on a franchise agreement of you own choosing. The critical analysis will be six-to-eight pages in length, and in it, you will identify the fundamental components of the agreement and why each component is necessary to the success of a franchise contract. The project is divided in to three milestones, which will be completed in Modules Two, Three, Four.
Objectives
To successfully complete this project, you will be expected to apply what you have learned in this course and should include several of the following course objectives:
1. Appreciate the components of a franchise agreement
2. Understand the importance of fully reading a franchise agreement
3. Further develop critical thinking skills
Main Elements
The final paper will be double-spaced, using 12-point Times New Roman font, APA style formatting, and six-to-eight pages in length, not including the title page, resources, or the copy of the franchise agreement. The paper must contain the following element, in the order presented:
Summary:
Provide a short two-to-three-paragraph overview of the paper.
Critical Assessment:
Assessment of your chosen franchise agreement should include the following:
· Quotes from franchise agreement
· Citations from articles
· Suggested corrections
Conclusion:
Conclude your assessment by answering the following questions:
· Is this agreement solid? Why?
· Does it protect the franchisee or franchisor more? Why?
· Would you sign it? Why?
Copy of franchise agreement used to conduct the assessment
Reference list
Format
Milestone One: Review
In 2-3 Franchise Agreement Analysis: Review, you will review the Franchise Agreement Analysis document. There is no submission for this milestone and it will not be graded separately.
Milestone Two: Continue Work
In 3-4 Franchise Agreement Analysis: Continue, you will continue working on your Franchise Agreement Analysis Paper. There is no submission for this milestone and it will not be graded separately. The final paper is due in Module Four.
Milestone three: Submit Final Paper
In 4-3 Franchise Agreement Analysis: Finalize, you will submit your final Franchise Agreement Analysis Paper. It should be a complete, polished artifact containing all of the main elements of the final project. This milestone will be graded using the Franchise Agreement Analysis Rubric.
Franchise Agreement Analysis Rubric
Requirements of submission: Written components of projects must follow these formatting guidelines when applicable: double spacing, 12-point Times New Roman font, one-inch margins, and APA citations. The paper should be 4-5 pages in length, not including the cover page, the resources, or copy of the franchise agreement.
Instructor Feedback: Students can find their feedback in the grade book as an attachment.
Critical Elements
Distinguished
Prof ...
PROJECT SCOPE STATEMENTPURPOSE Generally describes the proje.docxtarifarmarie
PROJECT SCOPE STATEMENT
PURPOSE: Generally describes the project’s deliverables and the work required to create those deliverables. The project scope statement provides a common understanding of the project scope among all project stakeholders and describes the project’s major objectives. It also enables the project team to perform more detailed planning, guides the project team’s work during execution, and provides the baseline for evaluating whether requests for changes or additional work are contained within or outside the project’s boundaries.
Project ID
NNNNNN-NN
Date
MM/DD/YY
Project Name
Prepared By:
Project Objectives
Project objectives include the measurable success criteria of the project, e.g., “SMART.” Projects may have a wide variety of business, cost, schedule, technical, and quality objectives. Project objectives can also include cost, schedule, and quality targets. Each project objective has attributes such as cost, volume, etc., a metric, and an absolute or relative value.
Product Scope Definition
Describes the characteristics of the product, service, or result that the project was undertaken to create. These characteristics will generally have less detail in early phases and more detail in later phases as they are progressively elaborated. While the form and substance of the characteristics will vary, the scope description should always provide sufficient detail to provide later project scope planning. Build off the high level scope statement as provided in the Project Charter.
Project Requirements
Describes the conditions or capabilities that must be met or possessed by the deliverables of the project to satisfy a contract, standard, specification or other formally imposed document. Analyses of all stakeholder needs, wants, and expectations are translated into prioritized requirements.
· Requirement #1
· Requirement #2 …
Resource Requirements
Describes the resource requirements, and whether resources will be acquired internally, externally, or a combination thereof.
Project Boundaries (Inclusions and Exclusions)
Identifies generally what is included within the project. It also states explicitly what is excluded from the project, if a stakeholder might assume that a particular product, service, or result could be a component of the project.
Critical Success Factors
Document the factors that will ensure the success or failure of the project.
Project Deliverables
Deliverables include both the outputs that comprise the product or service of the project, as well as ancillary results, such as project management reports and documentation. They describe what the clients will get when the project is completed.
Product Acceptance Criteria
Defines the process and criteria for accepting completed products.
Project Constraints
List and describe the specific project constraints associated with the project scope that limit the team’s options. For example, a predefined budget or any imposed dates that are issued by the cu.
IMPORTANT label each projects title page as follow Project 1P.docxsheronlewthwaite
IMPORTANT: label each projects title page as follow
Project 1
Project 2
Project 3
Project 4
Project 5
Note: Project 1 has to be completed by July 30th 2019,
Project 2,3,4,5 can be done before or by August 13th 2019
PROJECT 1 (Due on 7/30/2019 )
Scenarios
As a newly assigned project manager for the Ohio Department of Human Services, you are excited about working with technology projects throughout the state. The Ohio Department of Human Services' (ODHS) Office of Network Support (ONS) is responsible for managing the network and software applications for over 15,000 state and county agency employees throughout Ohio's 88 counties. The office coordinates software upgrades and network modifications from an operations center located in the capital, Columbus, with assistance from local technology employees in each of the county seats.
The position is not without its challenges, however. The network infrastructure throughout the state ranges from high quality, high-bandwidth connections in major population centers to older, partially working connections in the poorer, more regional counties. Additionally, budget and resources are a constant issue, with a high turnover rate among existing employees and an emphasis on outsourcing the labor force to several vendors to accomplish the myriad of support and project tasks. Your initial assignment is to examine the viability and costs associated with upgrading the existing e-mail, with the objective of developing the implementation project for the organization. ODHS had adopted the e-mail software called Globalupgrades (a Worldviewupgrades product) as its e-mail standard in 1994 and executed minor upgrades since then. However, the latest version of Globalupgrades, Version 9.0, contains significant enhancements desired by the ODHS user base, and the existing Version 7.0’s support will be phased out in the next year by Worldviewupgrades. The Worldviewupgrades sales representatives have been offering discounts for a Version 9.0 license, but the costs are approximately 20% more than previous licenses. Additionally, several other e-mail product vendors are lobbying state officials for business, some of them offering significant incentives. Generally, these products are viewed as less robust than Globalupgrades, but there are some segments of the user community that are supportive of these other options.
You are reviewing the existing documentation on the current state of the e-mail system, including license agreements and the Worldviewupgrades Globalupgrades 9.0 preliminary proposal. You are also examining the staffing structure and developing ideas on how to accomplish this task. In two weeks, you will need to brief the ONS Director on your planned approach to completing this effort.
Assignment Requirements project 1
3-4 pages (APA FORMAT)
Includes a Title Page (APA format)
1 reference page
List all References in APA FORMAT
1.Develop a high-level project charter for the E-Mail Upgrade Project des ...
Similar to Options analysis template in major feasibility study (20)
Levelwise PageRank with Loop-Based Dead End Handling Strategy : SHORT REPORT ...Subhajit Sahu
Abstract — Levelwise PageRank is an alternative method of PageRank computation which decomposes the input graph into a directed acyclic block-graph of strongly connected components, and processes them in topological order, one level at a time. This enables calculation for ranks in a distributed fashion without per-iteration communication, unlike the standard method where all vertices are processed in each iteration. It however comes with a precondition of the absence of dead ends in the input graph. Here, the native non-distributed performance of Levelwise PageRank was compared against Monolithic PageRank on a CPU as well as a GPU. To ensure a fair comparison, Monolithic PageRank was also performed on a graph where vertices were split by components. Results indicate that Levelwise PageRank is about as fast as Monolithic PageRank on the CPU, but quite a bit slower on the GPU. Slowdown on the GPU is likely caused by a large submission of small workloads, and expected to be non-issue when the computation is performed on massive graphs.
Learn SQL from basic queries to Advance queriesmanishkhaire30
Dive into the world of data analysis with our comprehensive guide on mastering SQL! This presentation offers a practical approach to learning SQL, focusing on real-world applications and hands-on practice. Whether you're a beginner or looking to sharpen your skills, this guide provides the tools you need to extract, analyze, and interpret data effectively.
Key Highlights:
Foundations of SQL: Understand the basics of SQL, including data retrieval, filtering, and aggregation.
Advanced Queries: Learn to craft complex queries to uncover deep insights from your data.
Data Trends and Patterns: Discover how to identify and interpret trends and patterns in your datasets.
Practical Examples: Follow step-by-step examples to apply SQL techniques in real-world scenarios.
Actionable Insights: Gain the skills to derive actionable insights that drive informed decision-making.
Join us on this journey to enhance your data analysis capabilities and unlock the full potential of SQL. Perfect for data enthusiasts, analysts, and anyone eager to harness the power of data!
#DataAnalysis #SQL #LearningSQL #DataInsights #DataScience #Analytics
Adjusting primitives for graph : SHORT REPORT / NOTESSubhajit Sahu
Graph algorithms, like PageRank Compressed Sparse Row (CSR) is an adjacency-list based graph representation that is
Multiply with different modes (map)
1. Performance of sequential execution based vs OpenMP based vector multiply.
2. Comparing various launch configs for CUDA based vector multiply.
Sum with different storage types (reduce)
1. Performance of vector element sum using float vs bfloat16 as the storage type.
Sum with different modes (reduce)
1. Performance of sequential execution based vs OpenMP based vector element sum.
2. Performance of memcpy vs in-place based CUDA based vector element sum.
3. Comparing various launch configs for CUDA based vector element sum (memcpy).
4. Comparing various launch configs for CUDA based vector element sum (in-place).
Sum with in-place strategies of CUDA mode (reduce)
1. Comparing various launch configs for CUDA based vector element sum (in-place).
ViewShift: Hassle-free Dynamic Policy Enforcement for Every Data LakeWalaa Eldin Moustafa
Dynamic policy enforcement is becoming an increasingly important topic in today’s world where data privacy and compliance is a top priority for companies, individuals, and regulators alike. In these slides, we discuss how LinkedIn implements a powerful dynamic policy enforcement engine, called ViewShift, and integrates it within its data lake. We show the query engine architecture and how catalog implementations can automatically route table resolutions to compliance-enforcing SQL views. Such views have a set of very interesting properties: (1) They are auto-generated from declarative data annotations. (2) They respect user-level consent and preferences (3) They are context-aware, encoding a different set of transformations for different use cases (4) They are portable; while the SQL logic is only implemented in one SQL dialect, it is accessible in all engines.
#SQL #Views #Privacy #Compliance #DataLake
The Building Blocks of QuestDB, a Time Series Databasejavier ramirez
Talk Delivered at Valencia Codes Meetup 2024-06.
Traditionally, databases have treated timestamps just as another data type. However, when performing real-time analytics, timestamps should be first class citizens and we need rich time semantics to get the most out of our data. We also need to deal with ever growing datasets while keeping performant, which is as fun as it sounds.
It is no wonder time-series databases are now more popular than ever before. Join me in this session to learn about the internal architecture and building blocks of QuestDB, an open source time-series database designed for speed. We will also review a history of some of the changes we have gone over the past two years to deal with late and unordered data, non-blocking writes, read-replicas, or faster batch ingestion.
Adjusting OpenMP PageRank : SHORT REPORT / NOTESSubhajit Sahu
For massive graphs that fit in RAM, but not in GPU memory, it is possible to take
advantage of a shared memory system with multiple CPUs, each with multiple cores, to
accelerate pagerank computation. If the NUMA architecture of the system is properly taken
into account with good vertex partitioning, the speedup can be significant. To take steps in
this direction, experiments are conducted to implement pagerank in OpenMP using two
different approaches, uniform and hybrid. The uniform approach runs all primitives required
for pagerank in OpenMP mode (with multiple threads). On the other hand, the hybrid
approach runs certain primitives in sequential mode (i.e., sumAt, multiply).
Analysis insight about a Flyball dog competition team's performanceroli9797
Insight of my analysis about a Flyball dog competition team's last year performance. Find more: https://github.com/rolandnagy-ds/flyball_race_analysis/tree/main
STATATHON: Unleashing the Power of Statistics in a 48-Hour Knowledge Extravag...sameer shah
"Join us for STATATHON, a dynamic 2-day event dedicated to exploring statistical knowledge and its real-world applications. From theory to practice, participants engage in intensive learning sessions, workshops, and challenges, fostering a deeper understanding of statistical methodologies and their significance in various fields."
2. Project Summary
Region/Unit
Location
Program
Project Number
Project Description
Document Control
Prepared by: Name
Title: Job title
Branch: Branch
Division: Division
Location: Floor, street, city
Version no: 0.1
Version date: dd mm yyyy
Status: Initial Draft/Consultation Draft/Approved Document/Minor Revision/Major Revision
DMS ref. no: DMS reference number
File/Doc no: File number/document number
Version history
Version no. Date Changed by Nature of amendment
0.1 Initial draft.
Project
Proposal
Options
Analysis
Business
Case
Project
Plan
Handover
Report
Completion
Report
4in1 Template
4. Endorsement and Approval
Customer (delete for Project Plan)
I agree to the project proceeding as proposed in this document.
Name
Position
Signature Date
Comments
Sponsor
I agree to the project proceeding as proposed in this document.
Name
Position
Signature Date
Comments
The following officers have endorsed this document:
Name
Position
Signature Date
Add further names as required
Project manager:
I recommend the project proceeds as proposed in this document.
Name
Position
Signature Date
5. Table of contents
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 2 of 31
6. Read this guidance text box before proceeding.
This template is used for Proposal, Options Analysis, Business Case and Project Plan.
Where it is being used for a planning study/strategy/policy development project, it would be completed for
proposal, and possibly options analysis. The business case would be retitled Organisational Delivery Plan
and a project plan would not be required, as the recommendations will be delivered by others.
It contains a project management plan that covers from the present until the next major milestone in detail,
and the remaining steps in outline form.
The ‘Project Plan’ term has been reserved for the implementation phase since OnQ’s inception in 2000.
Using the term ‘project management plan’ throughout overcomes the difficulty of preparing the wrong
template at the wrong time, just to have a management plan.
To create templates after the proposal, start with this template from the website, as it may contain updates,
and the previous template may have left out some sections not relevant to that part of the process then but
relevant now. Then bring material in Sections 1 to 6 forward from the previous template, bold italicising that
text. Insert any new material in normal typeface, enabling a reviewer/approver to readily see what has
changed from the last approved document. This can be particularly useful when there is a long time lapse
between templates, and avoids unnecessary searching by the reviewer/approver. As this material is being
brought forward, check that all the material mentioned in the guidance has been covered and then delete
the corresponding guidance box.
Most sections contain guidance shown in yellow boxes and a content area denoted by a
placeholder symbol Type here. Other sections contain draft text that needs to be reviewed and
selected/amended/deleted as necessary.
When the template is complete and the guidance boxes removed, update the table of contents
by
right-clicking in it and selecting ‘Update Field’, then ‘Update entire table’.
Once approved, this document should be managed in accordance with the Department of
Transport and Main Roads Recordkeeping Policy.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Executive summary
Extract the key points of this document. The executive summary should not say anything that has not been
included in the body of the template. So it is usually best to write this section last i.e. after the rest of the
template has been completed. Items that typically need to be in this summary include:
• A brief description of the problem or opportunity to be addressed
• An outline of the scope
• An outline of the project objectives and benefits sought
• Key risks and issues
• A summary of the time, costs and resources to complete the next stage
• A summary of the recommended course of action.
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 3 of 31
7. To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
1 Purpose of this document
The purpose of this document is to (Delete from here to the relevant close bracket and delete
any subsequent options, then copy the remaining text from this guidance box into the ‘Type
here’ box below.. Note: Do not explain the project here.
Proposal -) identify the specific problem or opportunity to be addressed, document the rationale
behind/the need for the project, and obtain the customer’s agreement to the scope and method
of progressing, and funding to proceed to the next stage.
Options Analysis -) document the options investigated and obtain the customer’s agreement on
a preferred option to proceed to business case preparation.
Business Case -) finalise scope definition of and concept estimate for the selected option,
evaluate benefits and obtain the customer’s commitment to funding and agreement to the
project’s inclusion in the QTRIP.
Project Plan -) outline how the project will be implemented, and confirm that the project can be
delivered within the desired funding and timing.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
2 Definitions
In the table below, define any term the audience may not understand, including specific terms,
abbreviations and acronyms.
To delete this guidance text box, double mouse click in the left margin and then press delete.
Terms, abbreviations and acronyms Meaning
Customer Decision maker ‘owning’ the new asset
Sponsor Head of the delivery group
3 Governance
Once the following sub-sections are completed for the project proposal, there should be few changes in
following templates, other than staff/phase transitions or a change in strategic direction as a consequence
of the electoral cycle.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
The project will be/is being managed in accordance with the project management policy of April 2012 and
the principles on the OnQ website under governance. Governance arrangements for the project are set out
below.
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 4 of 31
8. 4 Key Roles
Identify key personnel in the proposed project in the table below. Each member of the team must be aware
of their roles and responsibilities. Note that these roles should be pushed to the lowest level that has the
span of control to make decisions.
Refer to the OnQ website for clarity on ‘roles and responsibilities’.
Where multiple agencies are involved that own different parts of the new/upgraded asset/network to be
created by this project, list the coordinating customer who will be responsible for obtaining agreement from
the others on required functionality when the project identifies any such issues. The other customers
should also be listed.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
The key project management roles are:
Project Customer [Name], [Position]
Project Sponsor [Name], [Position]
Concept Manager [Name], [Position]
Program Manager [Name], [Position]
Project Manager [Name], [Position]
Advisory Group (optional)
5 Project organisation structure
Consider adding a project organisational structure here. Refer to the OnQ website under Project
management> Governance>/Project Governance Model.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
6 Higher level requirements
This sub-section will generally be completed by a transport planning area for a transport strategy
development project that will recommend that a number of projects proceed to delivery. When the proposal
document is prepared for these projects, locate this strategic material and simply cut and paste, including
whichever of the following headings are relevant.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
7 Whole of government requirements/strategic focus
Consider the immediate priorities of the current government, and TMR’s longer term accountability to
sustain the operations and asset management of the State’s transport network. Describe how this project
contributes to these (sometimes competing) drivers.
Extra links to federal and state strategy documents can be found on the OnQ website under Resources>
External websites.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 5 of 31
9. Type here
8 Departmental corporate/strategic requirements
Outline the project’s relationship to the TMR strategic plan and Roads Connecting Queenslanders. Show
also how the project contributes to any departmental regional/area strategy/plan, corridor and link
strategies/plans, and any local government local area transport plan.
Note that, whatever the government priorities of the day, there is still a requirement to develop safe,
affordable, fit-for-purpose project solutions.
Regional Transport plans can be found on the TMR website in the projects alphabetical listing under ‘C’
titled ‘Connecting - ……..’.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
9 Portfolio management requirements
State which TMR portfolio this project is a part of. Transport infrastructure projects generally form part of
QTRIP, which although it has the word program in its name, is a portfolio under the PMI Portfolio
Management Standard definition. Mention any governance requirements of the portfolio relevant to this
project, such as
• inclusion in the QTRIP submitted to parliament,
• requiring an approved OnQ proposal document to get on this list four years out,
• requiring an approved OnQ business case two years out.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
10 Program management requirements
State which program this project is included in and managed under, at both the state and local level. The
state program may be national, state or local. Locally, the project may be managed in program groups that
collect some of the above together into either geographic area or project management phase. A project
may commence as part of a planning program, and then move into delivery or operations programs.
Note that current departmental policy is that for any project to be entered on the QTRIP, it must have an
approved proposal and any project less than two years out must have an approved business case.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
11 Business and program benefits of the project
What is the purpose of this project?
Enumerate both the strategic business benefits the project is intended to produce, and the delivery benefits
anticipated from including this particular project in this particular program in this particular way, e.g.
economies of scale in procurement or delivery, avoiding expensive re-establishment if the project is split or
the remote area has to be revisited to complete an adjacent job.
The desired benefits should provide a compelling case for the investment and also provide the
basis for assessment of benefits realisation. Specific and realistic targets should be set for
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 6 of 31
10. benefits that can be quantified.
The project purpose may be to achieve benefits that may include reducing (whole of life?) costs
for government/community through
• asset preservation,
• improving safety/reducing traffic accidents,
• improving operational functionality by reducing pollution/congestion/travel times,
• improving network functionality by improving flood immunity, improving accessibility, providing
regional capacity/resilience or supporting development etc.
Some benefits will be difficult/impossible to quantify, and those that can be quantified will generally be
calculated and reported at the business case.
If federal funding is required, a Strategic Merit Test in accordance with Nation Building Program (NBP)
guidelines will be required with the business case.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
12 Approvals
Advise the approvals required, apart from those on this document’s endorsement and approvals page
above. Larger projects may have additional approvals or gates, such as IIC/PAF gates, or may require
inter-agency concurrence. Consider also financial approvals related to the likely cost of the project and the
likely cost of major procurement items. Indicate the approval levels likely to apply.
Consider also the approval levels required for variations.
If federal funding is desired for a proposed project that is not committed as part of a National Partnership
Agreement with the Australian Government, a Strategic Merit Test is required to be provided with the PPR.
(Templates for both of these appear on the OnQ site> program management> Nation Building Program>
templates). For projects requiring a Strategic Merit Test, IIC endorsement for submission to the Australian
Government is required. Federal approval of a submitted PPR is required before tenders are called. See
project management method below for more details. There is also a federal legislative requirement for
open tenders to be called for projects with Australian Government funding (please consult with National
Programs).
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
13 Reviews and reporting
Indicate the reporting cycle, and any review requirements. Reporting is usually done on a monthly basis,
and larger projects may be subject to whole of government Project Assurance (PAF) requirements and or
IIC reviews. Where there is no internally required report format, the OnQ Monthly Project Report proforma
under Tools> proformas and worksheets can be used, together with the reporting requirements planner.
Federally funded projects have their own review requirements as follows:
• A monthly status report may be required for significant projects.
• A Post Completion Report (template appears under Programs management> NBP) is required within
six months of physical completion of a project with an Australian Government contribution.
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 7 of 31
11. To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
14 Project management method
TMR’s policy is that the OnQ project management methodology is to be used for all TMR non ICT projects.
OnQ has a maximum of 20 steps and 10 templates in its 4 phases. Two of its 10 templates (the BPA and
the BRS) are only used for business development projects. The Component Assignment Brief (CAB) may
be used in any project, and is useful for briefing an internal service provider unit. The need for the other
templates is determined by the scale and complexity of the project. Large, complex projects will generally
warrant preparation of all templates, while smaller, routine projects can appropriately skip or combine some
templates. Similarly, template length will vary considerably with the complexity of the project.
Large/complex projects may have a major feasibility study that obviates the need for an options analysis
template, with approvals being done by correspondence.
Federally funded projects require a PPR report to be prepared at various stages. These are Scoping (at
TMR Proposal), Development (at TMR Business Case) and Delivery (at TMR major contract approval).
These are federal program management documents covering only funding, strategic fit and outcomes,
benefits and risks. They do not cover all of the elements needed for TMR internal project management, and
so are no substitute for preparing the OnQ Four-by template at Proposal, Options Analysis, Business Case
and Project Plan stages.
An OnQ proposal will bring forward material from any corridor study/link/route investment strategy that an
NBP project may have, and will also provide the basis for management of TMR concept phase work.
Where the state wants federal money for planning/feasibility, an early milestone will be preparation and
submission of the federal Scoping PPR, or Strategic Merit Test where a project is not currently part of the
NBP. The project may then proceed to some form of feasibility investigation and report, which may be
approved via correspondence in lieu of completing an OnQ options analysis. (Note: The Proposal will have
contained the project management plan for the whole of the concept phase. However, where major change
has occurred, the project management plan will need updating, and this is best done by producing the
Options Analysis document. This will provide a revised project management plan for preparing the
Business Case and obtaining approval). An OnQ business case will be prepared next, and this will feed a
federal Development PPR and outline the OnQ development phase work. An OnQ project plan will then be
developed during this phase, and a federal Delivery PPR will be prepared before calling tenders. Following
the implementation phase of the project, the OnQ finalisation phase handover and completion reports will
be prepared.
PAF projects similarly have their own program management requirements that similarly do not coverall of
the elements needed for internal project management.
Some Type 2 projects may combine Options Analysis and Business case if only one practical option exists.
Small/routine projects may use the reduced set of Type 3 abbreviated templates.
A transport planning study/strategy/policy development project would complete a proposal, and possibly an
options analysis. The business case would be retitled Organisational Delivery Plan and a project plan
would not be required, as the recommendations will be delivered by others. This is consistent with the
process outlined in the Integrated Transport Planning Framework (ITPF) at
http://www.tmr.qld.gov.au/Projects/Name/I/Integrated-Transport-Planning-Framework.aspx.
The OnQ methodology therefore gives the palette of processes for management of any project, and the
project manager needs to select from this palette the actual method that will be used for this particular
project.
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 8 of 31
12. Advise the project Type, the steps to be carried out, and the templates to be prepared.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
15 Technical standards and processes
Departmental technical standards are set out on the department’s external website > business and industry
> technical standards and publications). List at least the principal ones and consider listing all standards
that apply.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
All relevant departmental technical standards will be followed. These include:
Type here
16 Project definition
Once the following sub-sections are completed for the project proposal, there should be few changes in
following templates, other than current situation and performance measurement of different phases.
For the proposal, some information for these sections will come from any portfolio or program
planning/strategy document or link study that may have been prepared.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
17 Location
Describe the location of the proposed project. Insert a graphic of the location and describe the roads,
intersections or interchanges, etc involved. And/or refer to any annexed plans/visuals/diagrams, etc).
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
18 Background
Outline any research that has been done to justify this project. Identify why the proposed project is to be
undertaken, preferably from the perspective of someone with no prior knowledge of the project. Relevant
details may include:
• How the project need was identified (include such items as AADT, traffic volume, crash history
data, and any benchmarking or safety audit).
• Any other investigations, initiatives or projects carried out previously to address related issues.
• Previous consultation or community engagement, issues and outcomes.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
19 Current situation
Give details of any current issues, detailing the problem(s), need(s) and/or opportunities etc. together with
the issues this project will address.
Consider the impacts of the current situation on internal and external stakeholders, including the impacts of
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 9 of 31
13. not proceeding.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
20 Objectives
Describe the specific objectives of the project - the goals to be achieved, the issue to be resolved or the
rationale for undertaking the project. Objectives should relate to the benefits desired by the program and
portfolio that the project is part of, as detailed in 3.3.
These objectives should be reviewed and refined at the business case to ensure they are still relevant and
achievable.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
21 Proposed project
Given the above, describe the essential features of the proposed project in general terms, leaving detailed
specifics to the scope section.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
22 Delivery strategy
Where a particular delivery strategy/contract type becomes apparent, indicate this, together with the
rationale for selecting this approach. The Main Roads Project Delivery System (MRPDS) Feb 2009 Volume
1 provides guidance on developing an appropriate delivery strategy for road infrastructure projects. It also
describes the various contract types and provides assessment criteria for use in narrowing the range of
options.
Contract types include the Road Construction Contract (RCC), Roadwork Performance Contract (RPC),
Design and Construct Contract (D&C), Alliance Contract (AC), Early Contractor Involvement (ECI).
Relational Incentive Contract (RIC) and so on.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
23 Project performance measurement/success criteria/KPIs
Indicate how management of this phase of the project will be judged to have been successful. This may
range from a general statement through to a tabulation detailing what the Key Performance Indicators (KPI)
will be, how and when they will be measured and what the desired targets are. These may be in terms of
on time and within budget, or achieving particular milestones, and may also include measures such as
customer/ stakeholder satisfaction. Note that these are likely to change as the project progresses.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
24 Product performance measurement/success criteria/KPIs
Indicate the success criteria for achievement of the project operational objectives. Again, this may range
from a general statement through to a tabulation detailing what the Key Performance Indicators (KPI) will
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 10 of 31
14. be, how and when they will be measured and what the desired targets are. These will generally be known
quite early in the project, and data collection may need to be initiated to ensure there is a baseline before
any physical work commences, to measure the impact of the project against. Possible criteria include travel
time/queue length reduction, end user satisfaction, operating costs, pollution reduction etc. Refer to the
Post Implementation Report template for possible KPIs.
The project manager does not control the usage or network impacts of the project, so will not be in a
position to measure, or be held accountable for achieving these. However it is most important for the
project manager to know what is required so that ‘before’ measurements can be taken to enable later
comparison, and potential operating issues can be identified and escalated promptly to the customer.
These may include opportunities or threats to the final operation of the asset that is being created, or
decisions that need to be made that will have significant repercussions for subsequent operations.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
25 Project scope
For the proposal, some information for these sections will come from any project charter that may have
been developed by a portfolio or program planning/strategy document or link study.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
26 In scope
Identify the project boundaries. Also identify, to the level of detail appropriate for this template, the work
required to complete the project successfully. Project scope is defined in increasing detail as the project
moves from proposal, through options analysis to business case. It is then refined further during
preliminary and detailed design in the development phase.
Where possible include specific products or outputs.
A preliminary Predominant Type Cross Section is available from the OnQ site under tools> proformas. This
allows details to be entered in a word document, without the need for preparation in a CAD package by a
design office.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
27 Out of scope
State the work which will not form part of the project scope, and outline the risks to the project from these
out of scope work items not being performed by others.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
28 Constraints
Identify any restriction or limitation, either internal or external to the project that will affect its delivery.
Constraints may include budget, time, staff, developments/events, political circumstances, electoral cycle,
funding availability, environmental, native title and cultural heritage issues, permits, materials supply,
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 11 of 31
15. geotechnical conditions/testing, black soils, availability of key plant, seasonal weather conditions, legislative
requirements, immovable physical items etc.
Any known environmental and cultural heritage constraints should be listed. Note that during the concept
phase, an environmental scoping exercise will need to be conducted to identify existing environmental
values & constraints and possible legislative triggers to be further investigated. See the TMR
Environmental Management System for the steps required, at:
http://share.qdot.qld.gov.au/project/ems/Pages/InfrastructureProjects.aspx, entering ‘corp’ before your
username.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
29 Assumptions
Assumptions bring a degree of risk to the project, as they are often presumed to be true, are easily
overlooked and can appear to be not worth documenting. Examine your implicit as well as explicit
assumptions and list them, for your own protection. Some examples are:
• traffic volumes will continue to grow at ….%
• land that needs to be acquired can be obtained within the required timeframe
• key resources will continue to be available
• funding will continue to be available (e.g. following change of federal/state government).
Assumptions should be reviewed as part of the risk management process.
Particularly review the veracity of assumptions before finalising the business case.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
30 Related projects/proposals/planning studies
Identify any internal and external projects or proposals which may have an impact on this project or will be
impacted by it, such as other projects that may use the same resources or budgets, or may even have
been established to address similar needs.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
31 Urgency
Identify the urgency of the project stating reasons, for examples safety, political commitments, or funding
availability.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
32 Stakeholder impacts
A stakeholder is any person, group or organisation whose interests may be impacted by the project.
Identify them, and their interest in the project. Typical stakeholders are listed below
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 12 of 31
16. Possible stakeholders to consider
Political representatives (local, state and
federal)
Local community
Regulatory authorities
State government agencies - Treasury,
Infrastructure Queensland, EPA etc
Local governments
Local indigenous groups
Individual citizens
Special interest groups
Energy providers
Telecommunications providers
Media
Other areas of the department
Outback regional roads group
Property owners
Road users
Other projects
Impacts may be internal and/or external, positive or negative and may vary during the life of the
project (costs, disruptions, temporary arrangements etc.). Some of these may require culture
change and associated change management, either internally (where staff attitudes will be
important) or externally within the community affected. New
standards/policies/legislation/regulation may impact outside agencies and service providers.
Overview the stakeholder consultation carried out to date.
Complete/amend the following tables as appropriate. This section is meant to include the
standout stakeholders and groups only, to guide targeting of key messages in the external
communications plan. Thereafter it will remind the project of the original groupings and identify
for approvers any new group or major individual stakeholder that may emerge.
The following tables are not intended to substitute for the more detailed stakeholder records
and analysis done as part of Section 9.6 external communications plan.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
Internal
Stakeholder Impact/Interest in the project
External
Stakeholder Impact/Interest in the project
33 Options
Note: Where, after reading this guidance text, there is nothing to add in this section, delete the
subheadings and guidance and enter Nil here so the heading numbers remain the same.
Proposal – list any options to be considered in very broad terms only and delete the four sub- sections
below.
Options Analysis – complete the four sub-sections below, removing the words ‘Options Analysis document
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 13 of 31
17. only’
Business Case – This section may contain only a summary outline of other options considered and the
reasons for dismissing them, with the four sub-sections below deleted.
Project Plan – This whole section is generally not required.
To delete this guidance text box right-mouse click within this box, select Delete Rows.
Type here
34 Options Considered (Options Analysis document only)
Consider a range of feasible possibilities. Options may involve only parts of the project, and the analysis
may present relative or comparative costs for individual portions. Risk-adjusted estimates (of revenue,
costs, duration and benefits) may need to be applied to address project characteristics, level of knowledge
and degree of confidence in the estimates.
Note that while cost estimates of various options will normally be attached, the cost reported in the
following full section headed ‘Project Cost’ should be the total cost of the recommended option only.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
35 Assessment Criteria (Options Analysis document only)
The following assessment criteria can be considered:
• Rating of achievement of project and strategic objectives
• Cost, including potential revenues
• Economic benefit (net present value/BCR)
• Whole of life cost (maintenance, operations and depreciation)
• Public interest assessment/stakeholder impacts
• Legislative requirements and regulatory issues
• Whole of government policy issues/government priorities
• Procurement strategies
• Environmental/cultural heritage benefits/impacts
• Social benefits and their distribution
• Key assumptions and or risks
• Timing and sequencing of project delivery
• Constructability.
Attach results of analysis and evaluate these to determine the best option to proceed with.
Comparative costs should include land acquisition, PUP and Principal’s costs, as per the PCEM, where
these costs differ between options. Cost may be just one criterion, or it may need to be considered
separately and may be a go/no go item,
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 14 of 31
18. 36 Option Comparison (Options Analysis document only)
Options should be first evaluated against major ‘go/no go’ criteria and any option which does not meet
these criteria should not be considered further. Remaining options will then be compared.
One comparison method is weighted multi criteria analysis. This is carried out as follows:
• Identify the criteria and weightings for each criterion. Note that each criterion must be totally
discrete from the others. Weightings can be derived by agreement, or via a paired comparison
technique. Weightings are generally expressed as a percentage and values assigned by evaluating
their relative importance.
• Rate each option against each criterion. Use of a 1-10 scale is common.
• Add the weighted scores for all criteria for each option
Alternative methods include using a traffic light colouring system, or Low, Medium and High, classifications
rather than numeric values.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
37 Option Assessment (Options Analysis document only)
Assess the options. Include a qualitative description/summary of the advantages/strengths,
disadvantages/weaknesses and estimated comparative costs of the various options. Note that small
differences in total score may not necessarily identify the best option due to the level of accuracy of the
process.
Be sure to arrive at a conclusion. Until you can do that, you’re not ready to progress to Business Case.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
38 Project cost and quantifiable benefits
As per Annexure G of the Project Cost Estimating Manual (PCEM), complete the following stage estimates
for the following completions of this template:
Proposal Strategic estimate
Options Analysis Options analysis estimate
Business Case Business case estimate
Project Plan Detailed design estimate.
Attach the standard Project Cost Estimate (Summary) Form M4755 to this document and summarise it
below.
Some estimate of likely BCR should be made at Proposal stage. The CBA team can provide such advice
based on AADT, %CVs, length, type of works, roughness, anticipated flood immunity improvement and
viability of alternate routes. See http://rams/cba/ for their contact details.
Detailed BCR calculations using TMR’s CBA tool will be required for submission with the project Business
Case.
Complete/amend the following as necessary.
To delete this guidance text box right-mouse click within this box, select Delete Rows.
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 15 of 31
19. Type here
The date of the last stage estimate is …/…/…..
This estimate is a category (1 to 6) …..
The method of contingency estimation was deterministic/probabilistic.
The final figure given is a P90/50.
The confidence level in this estimate is very low/low/medium/high/very high.
Project Phase Total ($)
Concept
Development
Implementation
Finalisation
Base Estimate
Contingency
Total Project Cost
Escalation Amount
Out-turn Cost
Amount of any funding/contributions approved to date
Operating costs, including operations maintenance and any depreciation, are likely to be/have been
estimated at $......... per annum.
Quantifiable benefits/revenue are likely to be/have been estimated at $......... per annum.
The likely/calculated BCR is ………
Social, environmental or other considerations that indicate the project must be done are ….
39 Project management plan
Where this template is amended to become a program or portfolio level Organisational Delivery Plan (that
is the end point of a project that has completed a study or developed a strategy/policy identifying a number
of projects to be progressed), delete all of the following sub-headings and replace with a list of the
study/strategy/policy recommendations, indicating who will be required to progress which projects by when,
and how they will be funded.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
40 Scope
Add to or amend the following as appropriate to the template being prepared. Note that scope may be
impacted by the time available, the funds potentially available and the quality requirements for the finished
product, such as the design standards and surface finishes required, as detailed under sub-section 4 below
on quality.
Once scope is finalised, the project manager needs to be constantly on the lookout for any scope changes
and have them documented, costed and forwarded to the customer for decision. Failure to do this results in
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 16 of 31
20. scope creep. Approved variations for additional works are not scope creep, for the project manager at
least.
Review and amend the following as necessary.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Scope will be managed initially by proceeding through the concept and development phases to enumerate
the scope defined in Section 5 above.
An Environmental Scoping Exercise will also be conducted, which will identify existing environmental
values & constraints and possible legislative triggers to be further investigated, This will be done in
accordance with the TMR Environmental Management System and will be initiated by completing an
Environment & Heritage Service Request, (See InsideTMR> Tools and resources> Environmental
Management System).
Once scope is finalised, any changes will be identified, costed and their implications for time and quality
determined, using the OnQ site> tools> proformas> project change request and change log, or other
required/existing organisational process. Any changes to estimated cost will be handled through the cost
variation process in sub-section 3 below on cost.
41 Time
The plan for the concept phase and the indicative strategy for the remaining phases are outlined by the
milestone activities listed in the tables below. These tables will often suffice for the Proposal, but if a more
detailed electronic schedule has been prepared, it should be attached. Electronic schedules in Primavera
P6 are required for business case submission and for project plan.
Any proposed staging of the project should be mentioned.
Complete the tables below and review and amend the text following them as necessary.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Progress of the concept phase will be managed against the milestones listed below:
Milestone Date
Submission of project proposal for approval
Approval to commence Options Analysis
Select consultant from Registration of Interest (ROI) list
Prepare consultant briefs and offer documentation
Negotiate prices and gain financial approval
Commence Options Analysis
Complete strategic economic analysis on options
Approval to proceed to business case stage
Establish the preferred option
Complete business case
The following information will provide input to development of an electronic schedule for later phases.
Activity Planned Date
Business case approved
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 17 of 31
21. Activity Planned Date
Commence detailed design
Detailed design completed
Commence procurement
Contract award
Commence construction works
Construction works completed
As-constructed documents recorded
Progress will be reviewed and reported monthly, initially against the above milestones, and at later stages,
against the P6 schedule.
Extensions of time (EOTs) will be recorded in a change log for major contracts.
For projects that are mandated in RPM, TMR’s Reporting and Performance Management system, the
project manager will enter commentary on any time or financial variances, preferably as they occur, but by
the sixth working day of the month at the latest.
42 Cost
Extract the cost of completing this phase of the project from the Project Cost Estimate (Summary) form
M4755 into the table below. This will have been prepared in accordance with the Project Cost Estimating
Manual (PCEM). Note that the M4755 includes projected annual cash flow. It may be necessary in later
templates to provide estimated monthly cash flow. Note also that there are worksheets on the OnQ site
under Tools> proformas and worksheets to assist with basic costing and with financial impact analysis,
including revenue (if any).
Complete the table below for the current/coming phase and review and amend the text following it as
necessary.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 18 of 31
22. Type here
Activity Total ($)
Project Management
Total Phase Cost
The total project budget, formerly called allocations, will be obtained/managed through TMR’s State-wide
Program Investment Delivery Application (SPIDA). Variations to the project total budget will be initiated and
approved using the program submission form, formerly known as the M3131.
Approval to spend money on the project will be obtained in TMR’s Financial Approval Process (FAP)
system using the ‘Financial approval for purchase of materials and services’ form, formerly known as the
M739.
Staff and contractor staff working in-house will use CATS timesheets, and apportion their times to
appropriate cost codes determined by the project manager.
Expenditure will be recorded in SAP. General Ledger (GL) codes will be assigned to all expenditure, and
detailed estimate items aggregated to a suitable level into either SAP WBS elements or internal orders.
The structure of these needs to be determined by the project manager at the start of the job. The total of
these estimated items becomes the project management budget for each cost code/internal order, which
SAP expenditure will be monitored against.
SAP line items will be reviewed monthly, if necessary, to ensure no items have been charged to the wrong
cost code, and that any such items are corrected.
Expenditure forecasts will be done in Projman.
Expenditure will be reviewed and the forecast cost to complete will be estimated monthly.
Variations to project internal budget items will be identified by the project manager/team and submissions
requesting financial approval will be approved as per the limit of each officer’s financial delegation, with due
consideration being given to the impact on total project budget.
Variations that need to be funded from contingencies will be identified by the project manager/team and the
funds released by the program manager or the ‘major project owner’ for projects where the Major Projects
Contingency and Savings Management Policy applies.
For projects that are mandated in RPM, TMR’s Reporting and Performance Management system, the
project manager will enter commentary on any time or financial variances, preferably as they occur, but by
the sixth working day of the month at the latest.
43 Quality
Outline the anticipated quality requirements of the finished product. Consider geometric standards, such as
EDD/greenfields/brownfields requirements, surface finishes, environmental and cultural heritage
requirements and safety in design.
Where there is no required quality assurance format, the OnQ quality matrix on the OnQ site under Tools>
proformas and worksheets can be used.
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 19 of 31
23. Amend the following text and refer back to Section 3.8 as necessary.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
The quality requirements of the end product will be addressed during the concept phase process of
considering options and developing the business case. This process is designed to balance aspirations for
project scope, completion date, cost and quality, all of which impact upon each other. Design standards
and surface finish requirements will be considered in balancing these aspects of the project. Once these
matters are settled and the project proceeds to implementation, then the quality standards will be
incorporated into the contract brief and specification annexures.
44 Environment, cultural heritage and native title
The Environmental Processes Manual is the department's primary document establishing environmental
assessment, approval and management processes for transport infrastructure projects. The department's
Environmental System (EMS) has been developed to implement the requirements of this manual.
It can be found at http://share.qdot.qld.gov.au/project/ems/Pages/Home.aspx ).
Note that to access the EMS system, you will need to use your Novell password and username, with 'corp'
before the username. The EMS can also be accessed from insideTMR under the ‘Operations’ tab.
Beware native title on leases, camping reserves, sporting fields etc, especially in western areas.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Environment and cultural heritage will be managed in accordance with the Environmental Processes
Manual as per the TMR EMS under the Operations tab on InsideTMR.
45 Safety
A ‘Zero Harm’ policy exists within TMR which aspires to achieve an incident and injury-free work
environment where every person comes to work and goes home again safely.
This covers all activities, from the office based concept development, data collection and site investigations
through to operations. More detail will be given for the coming phase, than for later phases. Outline any
safety in design workshops/reports etc., and consider the safety of maintaining and operating the resulting
infrastructure.
Outline/include/attach the health and safety plan and any particular concerns relating to this project and
how those concerns will be managed.
All safety incidents and near-misses will be reported through Regional WHS coordinators, using WHS
hotline as per standard organisational practice. All personnel are required to comply with the WHS
legislation, relevant codes of practice, as well as site specific plans and rules as listed in site specific
induction.
Later completions of this template will require a project specific construction safety plan that is to be
approved before work on site commences.
Consider any mining traffic, paving material delivery, tourist traffic and other road users.
All project meetings during construction are to have safety on the agenda.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 20 of 31
24. 46 Functionality
The project manager needs to be alert to the general business and program benefits in Section 3.4, the
specific project objectives in Section 4.4 and the product success criteria in Section 4.7. The impact of
project decisions upon these needs to be considered, and where there is an impact, the customer should
be advised and provided with appropriate costed options. Where substantial improvements in functionality
become possible through performing additional work at additional cost, the customer may be willing to pay.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
Decisions on issues that could either reduce or increase functionality will be referred to the customer.
47 Human Resources
Identify the skills and resources required to deliver this and subsequent phases as appropriate. Consider
means of obtaining the resources and filling any skill/resource gaps by means such as internal transfer,
recruitment, secondment, consultancies, contractors or training internal staff. For large projects, consider
having an operator’s representative on the project team.
List the roles and general responsibilities that will form the basis of position descriptions.
Consider using the staff roles and responsibilities proforma and the Responsibility Assignment Matrix
(RAM) on the OnQ site under tools> proformas for the detailed assignment of responsibilities and tasks
once the resources are in place. These would be attached when this template is completed as a project
plan, and may, on occasion, be attached to others as well.
Consider also opportunities for professional development and skills transfer, as well as how performance
will be monitored and training requirements determined.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
48 Communications
External to project
Complete and attach the OnQ external communications strategy/plan and any necessary worksheets,
located on the OnQ site under Tools> proformas and worksheets.
This covers both community engagement and stakeholder management, both of which may involve similar
key messages and activities.
Community engagement is generally undertaken once in the concept phase, running concurrently with
stakeholder management. By the time this template is completed as a business case, community
engagement will have finished, and only stakeholder management will be required.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
External to project communication will be managed as per the attached external communications
management plan and worksheets.
Internal to project
Complete and attach completed OnQ internal communications plan and any necessary worksheets,
located on the OnQ site under Tools> proformas and worksheets.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 21 of 31
25. Internal project communication will be managed as per the attached Internal Communications management
plan and worksheets.
49 Risk
Proposal – Identify the risks to the concept phase and the overall or high level risks which may impact on
later phases of the project. These risks will be fully defined during preparation of the business case.
Ensure that property acquisition, environment, cultural heritage (including indigenous), flooding,
constructability, traffic managemnent, PUP and critical supply item risks are considered.
Options Analysis – Expand on the concept risk list and/or assess comparative risks. Consider commencing
use of the corporate risk management log.
Business Case and Project Plan – Attach completed corporate risk management log and include only the
higher level risks in the table below.
The TMR risk prompt list can assist with the identification of risks. It contains several hundred risks in a
number of categories. This list can be found at: http://tmrintranet/~/media/bf5ea575-e386-493f-a955-
c90b9929baaa/tmr%20risk%20prompt%20list.pdf
The Risk Management Log can be found at: http://tmrintranet/Policies-and-procedures/Risk-Advisory-
Unit/Risk-Management-Tools-and-Techniques.aspx and further information is available from the Risk
Advisory Unit (RAU) in Corporate Governance.
Complete the table below and review and amend the text following it as necessary.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 22 of 31
26. The table below identifies the major risks or uncertainties likely to be encountered in this phase as well as
the remaining phases of the project.
Risk details Comment on likelihood, consequence and
treatment
Overall Project Key Risks
Current Phase Risks
This list will be further developed by:
• taking these risks into the risk register in the corporate risk log,
• expanding as the project scope and impacts are fully developed,
• referring back to the corporate risk prompt list, and
• conducting (a) risk workshop(s).
• conducting (a) value management workshop(s).
• monitoring, reviewing and updating the risk register on a monthly/quarterly basis.
50 Procurement
Describe the methods to be adopted for procurement of the major consultancies/services to be engaged in
planning, preliminary/concept planning/design, environmental studies, geotech, survey, hydrological
studies, etc. These methods may include public invitation, private invitation from several suppliers on a
prequalified list, newspaper or telephone invitations. Sole offers may be used in some limited
circumstances, however their use should be kept to a minimum.
Departmental resources are available under the publication series and include the Manual – Consultants
for Engineering Projects, and MR 41/05 Prequalified Supplier Arrangement Manual. Various parts of the
organisation have panels of specialities which can also be used. Complete the table below and review and
amend the text following it as necessary.
Consider works packaging for economies of scale. Consider also the possibility of bulking up like works
and or materials, as well as the capacity of local industry and availability of critical supply items.
Later templates will include contract management arrangements, indicating who will be the principal’s
representative and agent, superintendant and representative, contract administrator etc.
Where there is no required procurement planning format, the procurement requirements matrix on the OnQ
site under Tools> proformas and worksheets can be used.
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 23 of 31
27. Amend the following text as necessary.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
The major consultancies/contracts/service providers required are listed below together with the proposed
procurement method:
Consultancy/Contract/Service
Required
Expected $ value Procurement method
Procurement will be in accordance with the State Purchasing Policy and will be carried out in accordance
with departmental procurement procedures including the Manual – Consultants for Engineering Projects,
and MR 41/05 Prequalified Supplier Arrangement Manual.
Any contracts will be managed using the TMR Contract Administration System (CAS) Manual/other
approved system.
All purchase orders will be processed in SAP and approval limits will be monitored in Projman.
Corporate Card will be used for purchase of small items provided these items are not cumulative to an
amount in excess of the current limit.
Requisitions for goods/services and purchase orders will be created in SAP.
Accounts will be processed and paid through SAP.
51 Integration
This project management plan has been prepared taking into account the requirements of all knowledge
areas, and so provides the means of integrating them, ensuring they can be progressed individually and as
a seamless part of the whole project with cohesive inter-relationships. Management against this plan using
the issues register on the OnQ site under tools> proformas will provide ongoing integration that will be
supported by the regular project meetings and reporting outlined in this plan.
52 Phase transitions/handover/completion
In the concept phase templates, identify any phase transition arrangements, such as handover from a
concept phase project manager to a delivery project manager.
The TMR document, data and information requirements for handover should be identified and costed as
part of the finalisation phase in the business case estimate.
The finalisation activities of handover and completion should also be included in the project schedule,
together with such activities as closing ledgers, producing as-constructed plans and updating systems such
as ARMIS and Asset Master.
At Business case and Project Plan, overview any known operational/traffic management issues, along with
intended commissioning arrangements that may be required for M&E equipment/operating systems, as
well as operations and maintenance manual preparation, asset transfer, handover, maintenance and
warranty arrangements as well as durability assessment report.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 24 of 31
28. 53 Design development
Within the OnQ methodology, design development is a ‘work management’ activity, not a ‘project
management’ activity. For road infrastructure projects, TMR uses the Design Development Report M4212
to document the design inputs and details. This record needs to be progressively completed throughout
concept and development phases. It documents the existing conditions, design considerations, parameters
and details, actions, technical decisions, design verifications and safety considerations. This will also
document normal design domain and any use of extended design domain and design exceptions.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Design considerations will be progressively documented in the Design Development Report M4212. As-
constructed plans will be prepared progressively during the implementation phase.
54 Project Learnings
There is a learnings register on the OnQ website under tools> proformas. One way of using this is to have
it in a directory area accessible to all team members who can add anything they wish to it as the project
progresses. This may be in very rough form, but the advantage is currency at the time of writing, and if
added to regularly by all, avoids losing learnings that may be forgotten by the time it comes to preparing
the completion report. Preparation of the completion report needs to resolve conflicting views that may
have been expressed in the register and present these concisely and cohesively. Of course, information for
this report will also be obtained from the project filing system and e-mail records.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Learnings on the project will be progressively entered into the learnings register from the OnQ website.
Project team members will add to this progressively throughout the project, and it will be an agenda item at
monthly team meetings. This will provide a source of information for preparation of the completion report at
the end of the project.
55 Recommendations
Summarise the key findings and make a recommendation on whether the project should proceed past this
point/gate to preparation of the next template in the series.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
<Project Name> Infrastructure T1/2 Project Proposal/Options Analysis/Business Case/Project Plan,
Transport and Main Roads, Month, Year Page 25 of 31
29. 56 Annexures
Annexures may include but not be limited to the following:
Locality Plan
Predominant type cross section
Project (Strategic) Cost Estimate (From PCEM).
Responsibility Assignment Matrix
External Communications Plan (OnQ proforma)
Internal Communications Plan (OnQ proforma)
To delete this guidance text box, right-mouse click within this box, select Delete Rows.
Type here
When the template is complete and the guidance boxes removed, update the table of contents
by
right-clicking on it and selecting ‘Update Field’, then ‘Update entire table’.
To delete this guidance text box, right-mouse click within this box, select Delete Rows.