Inputs
No |
Input |
Coming
from/Output Of |
Comment |
1 |
Project Manager’s Assignment Letter |
Company Specific Phase (This letter is depend on the organizational
hierarchy and business methodology.) |
For internal assignments |
2 |
Statement Of Work (SOW) (or Project Initiation Documents) |
Pre-Sales Phase |
For customer projects The statement of work is the document that identifies the project
scope, features and deliverables |
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
1.
|
Analyze SOW/assignment letter/Iteration scope to understand the
project goals, scope and requirements. |
PO |
SOW, Assignment Letter |
Understood Project |
TFS/AzureDevOps |
2.
|
Define the high level WBS according to the selected LCM. Identify project’s: 1-
Time-Box 2-
Releases planning using epics and FDD [1] 3-
Number of iterations 4-
Milestones (Like invoices) |
PO and Client Rep |
All Procedure Inputs |
Identified Work Products, releases and deliverables |
TFS/AzureDevOps |
3.
|
Identify standards that will be used in : 1-
Managing the projects developing the work products. 2-
Developing solution like life cycle ,modeling standard, and code
standards 3-
Quality standards 4-
Tools for each knowledge area : UML tools, Tracking Tools, Development
tools |
PO and processes responsible |
All Procedure Inputs |
Identified Standards |
PM_Project_Management_Plan_Template |
4.
|
Identify Requirement Elicitation plan. It should include : 1.
Identify and document acceptance criteria for
requirements elicitation procedures. 2.
Determine elicitation techniques for
requirements. |
PO |
|
|
PM_Project_Management_Plan_Template |
5.
|
Identify Data management. DM is the process of managing project data, in which format, from who. For example: old databases, Infrastructure setting-
Security guidelines. |
PO and team members |
All Procedure Inputs |
Identified Data management |
PM_Project_Management_Plan_Template |
6.
|
Identify skills and training needs for the project
success with project stakeholders from different areas (PD, CM, and QA). |
PO and team members |
All Procedure Inputs |
Identified Training |
PM_Project_Management_Plan_Template |
7.
|
Identify initial project/Iteration resources roles and
responsibilities for each process, procedure and activity by asking the
suitable representative. |
PO and team members |
All Procedure Inputs |
Identified Resources |
Project Management repository (Jira/DevOps/Trello) |
8.
|
Align Impact analysis: 1-
Internal TL/TL 2-
Cross functional Dev/Support/Operation |
PO and team members |
All Procedure Inputs |
Identified Resources |
Project Management repository (Jira/DevOps/Trello) |
9.
|
Group the resources in team and identify integration mechanism |
PO |
Partial
PMP |
Stored
Partial PMP |
|
10.
|
Create proof of concepts for required subjects |
Team |
Concepts |
|
Research Template |
11. |
Select issues needed to
DAR (Decision Analysis and resolution) |
PO |
Partial
PMP |
Stored
Partial PMP |
|
12.
|
Select DAR Evaluation Criteria. |
PO |
Partial
PMP |
Stored
Partial PMP |
|
13.
|
Identify Project Quality attributes and record them in the measurement
plan. |
PO and senior management |
|
|
Measurement
plan |
14.
|
Call the configuration management procedure for establishing the CM to
store the outputs. |
PO |
Partial
PMP |
Stored
Partial PMP And
TFS |
|
Outputs
No |
Output |
1 |
Approved
Partial PMP |
2 |
Research
template |
3 |
Initial
Measurements |
Implementation Guidelines
S# |
Guidelines |
1. |
Analyzing scope will help you
later in the estimation process if you depend on the scope to detect the
estimation parameters. In the scope, you can
define what is in and what is out of the scope. |
2. |
-Milestone is essential events
or activities that notify you the end of phase and a start of a new phase. That what you report to
the customer and track with him, because customer does not care with the
detailed activities. -Milestones are an event
that you care about within your project, like delivery or invoice. -Milestones can be
represented in MS Project as an attribute of the task. Just Check the flag [mark
task as milestone from task advanced tab]. -Deliverable here is what
you should deliver to the client according to the contract. In may include:
Software-training Manual and SW documentation. It may be the iteration
result of the solution in order to facilitate the business process for the
client. -You may also add new
column in the schedule for deliverables and set deliverables in this field.
*OR add it to the milestone notes field. |
3. |
Standards : Such as process standards,
standard templates and development standards. It helps also in the estimation
and may be the implementation of the project. |
4. |
LCM like: Waterfall, Incremental,
Iterative, Spiral and FirstScrum. That should be reflected
on the MS-Project plan. For Scrum you will have
iterations,, each release
represents release , which contains full waterfall life cycle. -In Agile, it will be
iterative time-box that will plan for releases and iterations within the
release and each iteration duration. |
5. |
-WBS is a tool to group
the project activities or work elements. It may be product oriented or
service oriented. -It is a tree structure. -You should develop the
WBS for outcomes not for actions. It helps you to plan for
cost, effort and resources for the project activities. Building the WBS need to
be deliverable-oriented in organized way as the standard. -How to build WBS from
MS-Project? You can build it from
Project->WBS and then define you WBS and create the details later on. |
6. |
Support tools Ex: PM tools, SW Engineering
tools and testing tools. |
7. |
Data management is the
data that project should collect, distribute, deliver and archive. Ex: Like old current system
screen shoots to build the new system with, Reports to design like it, and
Old system Database structure as a guide to build the new one. In addition, it contains
any non-configurable items. |
8. |
Skills and training
needs : It should take place in the plan if You can enter them or reference
to the Roles, Acronyms , Tools sheet in the quality system Ex: Training for analysis and implementation teams on
new methodologies and techniques. Training for
project management, quality control and quality assurance. |
9. |
Project Resources should include
human and non-human resources. It will be finalized in
the finalization procedure. Ex: -Ask QAM for assigning the
QAR -Asking the analysis
manager to assign requirement manager -Asking the CM manager to
assign the CC. You should define it in
the PMP resource sheet using the last update one on the quality system. -The new added columns
are: Role-Responsibility
and Email Address |
10. |
DAR Criteria: Criteria
should be traceable to requirements, scenarios, business case assumptions,
business objectives, or other documented sources. Types of criteria to
consider include the following: Technology limitations Environmental impact Risks Total ownership and lifecycle costs |
11. |
Each Quality attribute
should be identified how to be measured within the measurement analysis. Quality attributes may be: -Functionality -Reliability -Maintainability -Usability -Duration -Predictability -Timeliness -Accuracy You
should also consider these measurements from all related stakeholders |
12. |
Requirement
elicitation plan may include : Emp1 will meet
the customer or requirement provider at the beginning of the next
month to for 4 hours to elicit the requirements using use case models. |
13. |
elicitation
techniques may be : -Interviews -Meetings -Questionnaires. |
14. |
Requirement
provider may be: -External
customer -Internal
Customer -Management -Market Survey -Field Standard
for on-shelf applications. See CMMI
Reference page 487 in last tip |
Inputs
No |
Input |
1. |
Approved QA Plan |
2. |
Approved CM
Plan |
3. |
Approved
Candidate Requirements if needed. |
4. |
Use Cases if needed. |
5. |
Approved Partial PMP |
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
1. |
Select Predefined reference point for
estimation |
PO and Team |
Approved Partial PMP & Approved Candidate Requirements |
Selected Parameters |
TFS/AzureDevOps |
2. |
Conduct Sizing session for user stories
using poker technique[2]. |
PO and Team |
Estimation Guidelines |
Estimated Size |
TFS/AzureDevOps |
3. |
Documenting the following: ·
Scenario ·
Acceptance
Test ·
Assumptions ·
Constrains ·
Target
environment. |
PO and Team |
All Procedure Inputs |
Identified Assumptions, Constrains, Conditions and
References |
TFS/AzureDevOps |
4. |
Define project general working times and employees
specific calendars if found. |
PO and Team |
All Procedure Inputs |
General working times
defined |
TFS/AzureDevOps |
5. |
Determine the detailed WBS (Tasks) after analyzing the
available information. |
PO and Team |
All Procedure Inputs |
Identified Detailed WBS |
TFS/AzureDevOps |
6. |
Identify resources cost rates. |
PO |
Identified Assumptions, Constrains, Conditions and
References |
Identified Cost Rates and
Estimated Project Cost |
TFS/AzureDevOps |
7. |
Add activities additional expenses if
needed. |
PO |
Estimated Schedule |
Additional Cost defined |
TFS/AzureDevOps |
8. |
Finalize the Estimation of project human
and non-human resources. |
PO |
Estimated Effort and
Schedule |
Estimated Resources |
TFS/AzureDevOps |
Outputs
No |
Output |
1 |
Partial PMP |
2 |
Approved Size Estimation
Parameters |
3 |
Approved Effort
Estimation |
4 |
Approved Cost Estimation |
5 |
Approved Schedule
Estimation |
Implementation Guidelines
S# |
Guidelines |
1.
|
Project planning parameters include all information needed
by the project to perform the necessary planning, organizing, staffing,
directing, coordinating, reporting, and budgeting. Sizing parameters is settled by the judgment of expert
or historical data. CMMI reference page 403, tip 2. For Example: In initiation: use the project scope to detect the
operations and objects and classify it. In Analysis: Use the analysis document to detect the operations
and objects and classify it. Poker technique in Agile |
2.
|
Size estimation considered as a base for effort,
cost and schedule. Ex: Size is 10 simple UC and 10 Complex Effort = 10*Simple Hour factor for production +
10*complex factor for production. |
3.
|
Some of the assumptions may be considered as risks,
like missed information you build your planning on. For example you need a data entry activity and you
do not know the number of the books you will enter. |
4.
|
Ex: Each employee should provide his own calendar in
order to facilitate accurate planning. |
5.
|
-That means: Who does what when and including the
dependencies between activities. Dependencies include both the internal between
project tasks and external to external project tasks. -You should contact every process responsible in
order to develop the related tasks schedule. |
6.
|
Project cost may be a constraint on your project so
you should manage it carefully. |
7.
|
You can do that by adding the Fixed Cost field in the
MS-PMP. |
8.
|
Quantifying resources will be a judgment of the
sizing parameters and the project delivery constraint. |
Inputs
No |
Input |
1 |
Project scope |
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
1.
|
Release planning |
PO,Scrum Master, Team |
All
Procedure Inputs |
Closure Report |
|
2.
|
Iteration
planning |
PO,Scrum Master, Team |
|||
3.
|
Daily startup
meeting |
Scrum Master, Team |
|||
4.
|
Iteration
review |
PO,Scrum Master, Team,Customer |
|
|
|
5.
|
Iteration
retrospective |
Scrum Master, Team |
|
||
6.
|
Enterprise
architecture update -Requirements -Arch -Design -New features |
Enterprise architect |
|
|
|
7.
|
On the shelf
documentation update -Requirements -Arch -Design -New features |
Enterprise architect |
|
|
|
Outputs
No |
Output |
1 |
Process modification |
2 |
Release Backlog
prioritization |
3 |
Iteration Backlog
prioritization |
Inputs
No |
Input |
1. |
Historical Data (if exist) |
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
1. |
Assign a unique risk
identifier and define risks description according to the understand of
project nature. |
PM, Stakeholders |
All Procedure Inputs |
Identified Risks |
TFS/AzureDevOps |
2. |
Assess the category,
impact and probability of each risk. |
PM, Stakeholders |
Identified Risks |
Identified Categories ,
Impact and Probabilities |
(As Issues or risks) |
3. |
Assign a person for each
risk. |
PM, Stakeholders |
Identified Risks |
Assigned Persons |
TFS/AzureDevOps |
4. |
Plan for risk mitigation
and contingency for all risks. |
PM, Stakeholders |
Identified Risks |
Planned Mitigations and
Contingencies |
(As Issues or risks) |
Outputs
No |
Output |
1 |
Approved Risk Management
Plan |
Implementation Guidelines
S# |
Guidelines |
1. |
Use historical information
and plans assumptions to detect the risks. |
Contingency for highly
score risks. The frequency of tracking
the risk is relative to the tracking procedure. |
Inputs
No |
Input |
1.
|
Partial PMP |
2.
|
Approved Software
Development Plan |
3.
|
Approved QA Plan |
4.
|
Approved CM
Plan |
5.
|
Approved Measurement and
Analysis Plan |
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
1.
|
Review and consolidate
sub-plans that affect the project and resolve any conflicts. |
PM and relevant
stakeholders |
All Procedure Inputs |
Aligned Sub-Plans |
TFS/AzureDevOps |
2.
|
Plan for monitoring and
controlling the project: ·
Daily startup meetings ·
Scrum of Scrums ·
Retro's ·
Iteration Presentations |
PM and relevant
stakeholders |
Aligned Sub-Plans |
Planned Monitoring and
Control Activities |
TFS/AzureDevOps |
3.
|
Plan for stakeholder
involvement and update schedule as needed. |
PM and relevant
stakeholders |
Aligned Sub-Plans |
Planned Involvements |
TFS/AzureDevOps |
4.
|
Resolve the resource allocation
for the current iteration in case of multi iterations projects. |
PM and relevant
stakeholders |
|
|
TFS/AzureDevOps |
5.
|
Define the re-planning
criteria according to the scope and predefined assumptions and risks. |
PM and relevant
stakeholders |
Planned Monitoring and
Control Activities |
Identified Re-Planning
Criteria |
PM_Project_Management_Plan_Template |
6.
|
Review estimated planning
cost against the defined budget if found. |
PO |
|
Approved budget or modify
plan |
TFS/AzureDevOps |
7.
|
Plan for refactoring each
3 iteration, to have buffer for ½ iteration for XP refactoring process |
SM |
|
Approved budget or modify
plan |
TFS/AzureDevOps |
8.
|
Plan iteration reviews
and retrospective activities |
SM |
|
Approved budget or modify
plan |
TFS/AzureDevOps |
9.
|
Conduct Peer Review on
all plans in order to prevent the rework and defects on the plans. |
PM and relevant
stakeholders |
|
Plans reviewed |
TFS/AzureDevOps |
10.
|
Approve PMP from senior
management. |
PM and SM |
Updated PMP |
Approved PMP and Sub-plans |
Email or KOM |
11.
|
Conduct internal Kick-off
meeting (KOM) with all project team members to collect review project scope and
gather comments, then get commitments from all of them if needed. |
PM and Project Team Members |
Approved PMP and Sub-plans |
Obtained Commitments and
MOM |
TFS/AzureDevOps |
12.
|
Conduct customer KOM with
all customers to collect comments and obtain commitments if needed. |
PM, SM and Customer |
Approved PMP and Sub-plans |
Obtained Approval and MOM |
TFS/AzureDevOps |
13.
|
Apply CM repository
changes according to CM plan. |
CC |
Approved CM plan |
Updated CM Repository |
CM Repository |
14.
|
Baseline Management
Version |
CC |
Approved CM plan |
Updated CM Repository |
CM Repository |
15.
|
Baseline the project plan
and configurable items and then add output to the CM repository. |
PM |
Planning work products |
Baselined Planning Work products |
TFS/AzureDevOps |
16.
|
Publish the CM plan to
relevant stakeholders. |
PM |
Obtained Approval and MOM |
Published CM plan |
TFS/AzureDevOps |
17.
|
Notify the responsible
team members to execute the planned activities |
PM |
Baselined Project
Management Plan |
Notification E-mails |
TFS/AzureDevOps |
18.
|
Generate the project
Repository (Kanban Board) that contains: 1-
Backlog: the project tasks with its WBS in order to track with 2-
To do: what to do in this time-box 3-
Under Execution: Started Tasks 4-
Verify: finished Tasks and awaiting for verification 5-
Closed tasks: Finished tasks in the plan. |
PO and SCRUM Manster |
Baselined Project
Management Plan |
TFS Or Trello |
TFS/AzureDevOps |
Outputs
No |
Output |
1. |
Baselined PMP |
2. |
Baselined Software Development
Plan |
3. |
Baselined QA Plan |
4. |
Baselined
CM Plan |
5. |
Baselined
Candidate Requirements |
6. |
Baselined Estimation
Parameters |
7. |
Baselined Risk Management
Form |
Metrics
Metric |
Equation |
Accepted
Criteria |
CPI |
Automatic |
|
SPI |
Automatic |
|
SV |
Automatic |
|
CV |
Automatic |
|
EV |
Automatic |
|
Implementation Guidelines
S# |
Guidelines |
1. |
That activity should take
place in case of different responsible, but if the responsible is the same,
you do not need for that activity. For Example, If the PM,
CM, TL is the same. And a review on the QA
has been done with the PM, then you can consider this review here. Ex: PMP, PD, MA, Risk
Plans You should review all
organization plans that affect the project. |
2. |
-It is Recommended to
adjust the monitor and control process with the milestone review. -For
projects less than one month: it should be weekly or each 10 days. -For projects grater than one month: it should be weekly or each 10
days or bi weekly. |
3. |
Stakeholders includes : customers, end users,
developers, producers, testers,
suppliers, marketers, maintainers, disposal personnel, and others who
may be affected by, or may affect, the Product as well as the
process. |
4. |
You can do that be using
the MS-Project Reports->Assignment->Over-allocated Resources. |
5. |
Ex: You should re-plan your
project if the cost variance is greater than 10% Or project duration
variance in 20%. So you should baseline
your plans in order to measure. Also any awaiting
information from the clients. |
6. |
You can detect it from the
MS project using the view->Reports-> Over
View->Project Summary Report. The
defined budget comes from the assignment letter or the SOW |
7. |
Approval means
: Approve
resources, schedule and budget for master and detailed plans. |
8. |
-All team members should be
available in this meeting. -Also you should discuss
the involvement matrix within the meeting to assure the interaction between
different resources. -Clarify any details
about project organization structure and CM repository. -Attendance of QC team is
very important in order to find the alternative paths and other exceptions
that may appear in the use case handling. |
9. |
For External Customer,
it's recommended to do the KOM. However, some times you
just need a notification throw available communication channels, as if change
requests projects. |
10. |
The RTM is ready now and
may be a CI. You should baseline the
plan in order to track with the defined baseline. For base lining the
MS-Project plan, go to Tools->Tracking->Set Baseline. |
11. |
It can be throw the CM
repository or a shared folder. |
Inputs
No |
Output |
1 |
Baselined PMP |
2 |
Measurement
and Analysis Plan |
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
1. |
Conduct daily startup
meeting to review: ·
What is done ·
What blocks the remaining? ·
What to do today ·
Missing assets, work products to facilitate the project |
SM & PO |
TFS/AzureDevOps |
||
2. |
Update your project boards
by the progress, and create/remove/edit tasks in order to support objectives |
SM & PO Or all Team members |
TFS |
Updated TFS |
TFS/AzureDevOps |
3. |
Re-Calculate the planned end
date according to the remaining planned activities. |
SM & PO |
Baselined Project
Management Plan |
Tracked Activities |
TFS/AzureDevOps |
4. |
Build/review burn-up chart
in order to evaluate the previous state, and remaining activities. Already embedded in TFS |
SM & PO |
TFS |
TFS |
TFS/AzureDevOps |
5. |
Track project schedule,
cost and effort and all issues that slow down the team progress. Ex: It called impediments[3]
in agile model, and have a special section in TFS to track. |
SM & PO |
Activities Reports |
Project Tracked Schedule |
TFS/AzureDevOps |
6. |
Track Project milestones:
Key events and deliveries within the project |
SM & PO |
TFS |
TFS |
TFS/AzureDevOps |
7. |
Track and update project
risks according to the collected data. |
SM & PO |
Activities Reports |
Project Tracked Risks |
TFS/AzureDevOps |
8. |
Assure that risks
mitigation plans implemented if risks occurred |
SM & PO |
Activities Reports |
Project Tracked Risks |
TFS/AzureDevOps |
9. |
Track project Resources
and involvement matrix. |
SM & PO |
Activities Reports |
Project Tracked Resources |
TFS/AzureDevOps capacity
board |
10. |
Track Data management. |
SM & PO |
Activities Reports |
Project Tracked data |
TFS/AzureDevOps
impediments |
11. |
Collect/Calculate
measurement data according to the measurement plan. Review configuration
management process |
SM & PO |
Data Collection Mechanism |
Collected Measures Data |
TFS/AzureDevOps Reports
and dashboards |
12. |
Collect users/customers
feedback from: 1-
Working environment 2-
Google/Apple Stores[4] 3-
Performance issues by Firebase 4-
Crashlitics by Firebase 5-
Other sources of information Then you should assign
tasks to relevant stakeholders |
SM & PO |
Data Collection Mechanism |
Collected Measures Data |
TFS/AzureDevOps Reports
and dashboards |
13. |
Analyze measurement data
according to the predefined procedures. |
SM & PO |
Collected Measures Data & Analysis Procedure |
Analysis Reports |
TFS/AzureDevOps reports
and dashboards |
14. |
Review the analysis
results in order to refine existing measures or add new measure if necessary. |
Reviewer SM |
TFS |
TFS |
TFS/AzureDevOps |
15. |
Prepare the project tracking
report according to the frequency defined in PMP and project schedule. |
SM & PO |
TFS |
TFS |
TFS/AzureDevOps |
16. |
Prepare and conduct
iteration review meeting with stakeholders (internally and/or externally)
for discussing the project status and take decisions if
needed. Iteration review/
retrospective/release review. The output should be
reflected on the process for next step. |
SM & PO and
Stakeholders |
Updated Process and
actions |
Updated Process and
actions |
Updated Process and
actions |
17. |
Record iteration review
variances. ·
Bugs by QC ·
Tasks by Scrum master |
SM & PO and
Stakeholders |
Updated Process and
actions |
Updated Process and
actions |
Updated Process and
actions |
18. |
Identify Alternative
Solutions to solve issues for issues related to DAR. |
SM & PO |
Updated Process and
actions |
Updated Process and
actions |
Updated Process and
actions |
19. |
Select Evaluation method
mechanism. Typical evaluation methods
include the following: -Modeling and simulation -Engineering studies -Manufacturing studies -Cost studies -Business opportunity
studies -Surveys -Extrapolations based on
field experience and prototypes -User review and comment -Testing -Judgment provided by an
expert or group of experts (e.g., Delphi Method) |
SM & PO |
Updated Process and
actions |
Updated Process and
actions |
Updated Process and
actions |
20. |
Identify Alternative
Solutions to solve issues for issues related to DAR. |
SM & PO |
Updated Process and
actions |
Updated Process and
actions |
Updated Process and
actions |
21. |
Evaluate alternatives and
select the best according to the defined criteria. |
SM & PO |
Updated Process and
actions |
Updated Process and
actions |
Updated Process and
actions |
22. |
Take and track the
suitable corrective actions and assign responsibilities for executing any
corrective actions. |
SM & PO |
Updated Process and
actions |
Updated Process and
actions |
Updated Process and
actions |
23. |
Prepare and conduct a
review meeting with SM for discussing
the project status and measurement analysis reports to decisions, and send copy of PM
status report to QA to be updated if needed. |
SM & PO |
Initial Milestone Go/No Go
Decision |
Approved Milestone Go/No
Go Decision |
PM_MOM_Form |
24. |
Make suitable updates for sizing
parameters estimation and project plan if needed, and communicate
changes to relevant stakeholders. |
SM & PO |
Adjusted Plan |
Adjusted Plan |
Adjusted TFS Plan |
25. |
Make suitable updates for
your management process to achieve project commitments, goals
and meet QPM metrics and measurements. |
SM & PO,team ,EPG |
Updated Process and
actions |
Updated Process and
actions |
Updated Process and
actions |
26. |
Align project plan with
all related plans within the organization |
SM & PO |
Updated Process and
actions |
Updated Process and
actions |
Updated Process and
actions |
27. |
Collect improvement information
during the retrospective by gathering the following information: 1-
What 2- Continue 2-
What 2-Imporve 3-
What 2-Stop Over the following areas: 1-
Planning 2-
ANS 3-
Arch and design 4-
Implementation 5-
Testing |
All team members |
Updated Process and
actions |
Updated Process and
actions |
Updated Process and
actions |
Outputs
No |
Output |
1. |
Approved Tracking Reports |
2. |
Approved Corrective Actions |
3. |
Updated plans |
Metrics
Metric |
Equation |
Accepted Criteria |
CPI |
Automatic |
90% |
SPI |
Automatic |
90% |
SV |
Automatic |
90% |
CV |
Automatic |
90% |
EV |
Automatic |
+ |
Re-work% |
Rework Effort/Iteration
power |
5% |
Velocity |
No. points done by the team |
As planned |
Cycle Time |
Difference between the
start operation time and end operation time to finalize the iteration
objective, which includes the operation overheads that should be removed and
optimized. |
0 |
Implementation Guidelines
S# |
Guidelines |
1. |
Actual duration means the
time be spent in the activity not the duration. So you should update the
following information: -Actual start. -Actual End. -Actual Work. The actual
work represents the effort. It can be from the agile
workspace on the wall. You can enter any
additional information you need to help you tracking your project. |
2. |
-For WBS status, add the %
complete field and then use the grouping of WBS levels to know the status of
each package. -for not started or
finished tasks, open project menu->Filters->More filters->Select
Should Start/Finish by and then press edit and press show in menu. Now you can select it from
the filter menu. -Also you can insert
progress line to view visually the late activities due to the current
progress date. All shifted activities to
the left should have progress to the progress line. -How to Print MS-Project
reports as PDF? You can do it by setting
the default printer to "Adobe PDF" after installing the Adobe
Acrobat reader. -It may include internal
and external activities. -You can simplify the
"Should have started tasks" to show the successor or not from
report details. |
3. |
Critical task is the tasks
that affect the critical tasks. You may need to track the
variance or performance between schedule and cost throw the PM measures like:
CV-CV% -SV-SV%-CPI-SPI. |
4. |
-You can derive it from
the Microsoft project ->View->Reports-> Overview->Milestones. Change the report type to
"variance". To print the report
correctly, do the following: -set your layout to
Variance -Adjust your fields to
work correctly specially the date fields. -Show all project levels |
5. |
Resource example:
Resources availability and knowledge. |
6. |
Through data management
sheet in PM tracking. For example: We can record what data
you received, what is remaining, and when we will get it. |
7. |
This task should include
the milestone review as planned. |
8. |
Note that the deviation normally
occurs; perform corrective actions for significant deviations. -issues may be related to
schedule, budget and cost or any additional issues to face or may support the
project. In addition, you represent
it by an action items in the tracking sheet. See CMMI Reference, page
418. |
9. |
This task should include
the milestone review as planned. |
10. |
When monitoring, the
actual values will adjust the plan and then the involvement date of each
participant, so you should communicate the changes again to get commitments. That can be achieved
automatically by centralizing the plan on the CM repository or shared working
folder. Plan changes are a result
of entering the actual values or replanting the activities. Also
it comes as a result from the re-planning. |
No |
Activity |
Res. |
Input |
Output |
Temp/Solution |
1.
|
Request from PD, CM, QA,
PR to prepare the following points considering organization guidelines: ·
Measurements objectives |
PM |
All Sub Plans |
Measurements Plan Suggestions |
TFS/AzureDevOps |
2.
|
·
Measures (Name, meaning and uses) |
||||
3.
|
·
Collection mechanism and
frequency ·
Collection source and destination. ·
Determine measures collector |
||||
4.
|
·
How to analyze the measures ·
Measures reporting frequency and reporting mechanism |
||||
5.
|
·
Suggestions of improvement to be added in the MA guidelines. |
||||
6.
|
Consolidate, Prioritize,
review and approve measurements plans in meeting with PM, PD, QA,CM and PR |
SM |
Measurements Plan |
Approved Measurements Plan |
TFS/AzureDevOps |
Inputs
No |
Input |
1 |
Approved Tracking Reports |
3 |
Approved Risk Management Actions |
5 |
Approved Acceptance Test Defect
Summary Report |
6 |
Customer Formal
Acceptance |
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
8.
|
Prepare the project closure report using
the latest tracking report and milestone review. |
PM |
All
Procedure Inputs |
Closure Report |
TFS/AzureDevOps |
9.
|
Determine and
record lessons learnt. |
PM and Stakeholders |
All
Procedure Inputs |
Lessons Learnt |
TFS/AzureDevOps |
10.
|
Use the lessons
learnt to update the quality system. |
QAM |
Lessons Learnt |
Updated Quality system |
All Quality system templates and forms |
11.
|
Record
measurements data within organization measurements data For more
analytical data, we can classify project data with : *Project type *budget range *period |
PM And Top management |
|
|
|
12.
|
Collect
improvement information |
PM And EPG |
All project data |
Proposal for improvement |
|
13.
|
Conduct meeting
to analyze process data to extract experience gained in current process
enactment. |
PM and Stakeholders |
All
Procedure Inputs |
MOM |
PM_MOM_Form |
14.
|
Propose process
modifications if needed and suggest modifications for the process forms and
scripts. |
PM and Stakeholders |
All
Procedure Inputs |
MOM |
PM_MOM_Form |
15.
|
Prepares and conduct meetings for
discussing the project closure using the project closure report. |
|
Closure Report |
|
|
16.
|
Meets with the senior management
reviewing the project closure report and obtaining approval/signature on the
content and on formalizing project’s status as closed. |
PM |
Closure Report, Gained
Experience and Suggested Process Modifications |
SM Approval |
PM_MOM_Form |
Outputs
No |
Output |
1 |
Approved Closure Report |
2 |
MOMs |