The following are the problem solving tips of one of the students.There is not standard.And it is just for reference only. To really understand the essence of project management, please listen to the lectures and read the book carefully.
Topics about changes
Sequence: 1 Make a change request in writing (or record the change) – 2 Assess the impact of the change – 3 Go to a CCB meeting for decision making – 4 Communicate the decision – 5 Update the relevant documents – 6 Implement the change …. The whole process is recorded in the change log.
Changes made before the plan or baseline is approved.
Changes are mentioned at this point and do not need to go through the change control process.
Changes in Agile
Changes occur in Agile and do not require a strict change control process. Requirements in Agile are the responsibility of the PO Product Owner who embraces new requirements and prioritizes them at all times.
Contract type selection
For clear scope, choose a lump sum contract.For hired professionals, choose a quantity contract.For unclear scope or frequent changes later, choose a cost-reimbursement contract.
Problem Solving
Sequence: 1 Define the problem – 2 Root cause analysis – 3 Identify multiple solutions and evaluate options – 4 Implement the solution – 5 Evaluate if the problem is solved
Resource optimization
If the critical path is extended, choose resource balancing.If the critical path has not changed, choose resource smoothing.
Progress compression
If there is money, choose catch-up. If there is no money, consider the fast track approach.
Gathering requirements
If discussing across departments, choose lead generation techniques.
If looking for new ideas, choose brainstorming.
If categorizing the collected results, choose affinity diagrams.
If thoughtful silence focuses on the quality of ideas, choose the nominal group technique.
If targeting a thematic group and not just anyone who wants to participate, choose focus group sessions.
Project management sequence
Project charter (also, identify interested parties) – 2. Identify requirements – 3. Define scope (scope statement) – 4. Create WBS (and dictionary) – 5. Define activities – 6. Sequence activities ……. Once the plans for each area have been developed, go to 4.2 to consolidate and obtain approval from all relevant parties and then publish. (Note that the project management plan does not just need to be approved by the sponsor. It is approved by all key stakeholders, especially those responsible for specific tasks. How can they assign work if they don’t agree?)
Project kick-off meeting (kick-off)
This meeting is held at the end of the planning phase of the project, when the execution phase is about to begin. It is not held during the start-up phase.
Estimation methods
Analogous estimation with no detailed information is used when there is no WBS. It is the least accurate.
Parametric estimation:Whenever a formula is used, there is the parametric estimation.
Bottom-up needs details and WBS.It is the most accurate.
Order of managing risks
Identify risks (record to risk register) – Qualitative assessment – Quantitative assessment (as needed, sometimes not) – Develop responses – Implement responses – Monitor risks (How effective is the risk response?Are there any new risks emerging?)
Sequence of agile planning
1 The product vision.
2 Product road-map, i.e. release plan. Too many features should be split into multiple releases and identify the main features for each release.
3. Iteration plan. Determine how many user stories (or features) will be completed in the most recent iteration.
4. Split user stories or features into technical tasks (e.g. front-end work, back-end work) and estimate the workload.
Acceptance criteria
Project success criteria are in the project charter.Deliverable acceptance criteria is in the scope statement.
Quality tools
When you need to analyse whether two factors are related, select scatter diagram.
When control, out of control are shown in the title, choose control chart.
When the root cause is shown in the title, choose Ishikawa diagram or cause and effect diagram.
