Scenarios/Issues Flashcards
Which documents need and don’t need version control
List of Assumptions(config mgmt): Asuumptions can change over time as new info becomes available, important to track revisions..
Lessons Learned: No version control. Not subject to frequent revision, usually compiled and reviewed at end of project or phases.
SH Register: No version control. Undergoes minimal changes so version control not needed.
-Most SH identification done early in project, so minimal changes happen.
E.2.Q.120 Feature developed added complexity to product. Need to determine if the increased complexity is indeed slowing down the delivery of user stories.
Cycle time chart shows time taken to move US from start(WIP)->finish US(Done)
Cycle time: Measures amount of time takes for a US to move from start of development(WIP) to completion(Done)
-By checking cycle time chart, you can see if time take to complete US has increased since the added complexity is affecting team’s productivity.
-Cycle time is direct indicator of how quickly team is delivering value.
-If cycle time has increased, then confirms US are moving slower
Velocity: reviewing current points in SBL vs last 3 sprint velocity can provide insights, doesn’t give direct measure of how long it is taking to complete a user story
-Velocity can be impacted by various factors and might not indicate clearly the impact of increased complexity to an individual US.
Process to check Cycle time
1. Collect Data: Gather cycle time data from teams tracking tool
2. Analyze Trend: Look for trends over recent sprints, see if there’s an increase in cycle time after the introduction of new features.
3. ID Patterns: Determine if there is a consistent pattern of increased cycle time which correlates w/ the addition of new complexity.
4. Take action: If increase in cycle time confirmed, plan, and prioritize refactoring or other improvements to reduce complexity and improve efficiency.
Why would story estimating not math w/ the actual time/effort it takes to complete story? What did team not account for?
- Innacurate Initial Estimate: Team could have underestimated complexity and effort reqd because lack of understanding.
- Scope Creep: Scope for US might of expanded beyond initial estimate, leading to more work than anticipated.
Unforeseen Dependencies. - Technical Debt: Existing tech debt poor code quality can slow down development. Making it take longer than expected.
- Team Skill: Diff in team members skills and exp. Less exp member might take longer to finish task.
External Factors - Unclear Reqs: If reqs were not clearly defined or understood, might encounte unexpected complexities during devlmt
What is happening when you notice story cards(points) getting bigger each iteration?
Added scope? Or Technical debt?
Increase in Complexity: US can become more complex as project progresses.
Scope Creep: Might be increase in scope or requirements being added to the US, making them larger or more complex.
Improved understanding and Detail: As team gets more understanding of project and it’s reqs, might be adding more details and acc.crit to each US, resulting in higher story points.
Overestimation: From past exp.
Technical Debt Accumulation: If tech debt accumulating can make new dev tasks harder and more time consuming leading to higher estimates.
Agile PM talking through the defects raised so far. To get more accurate view of effort per card, you ask quality tester to begin tracking defect cycle time.
What will they report back?
Cycle time is how long work on a process takes.
A. how many defects were discovered in that iteration.
No iterations in kanban=Cycle times.
B. How long took to fix a defect from time it was found to time to fix.
C. How many cycles it takes to raise a defect for the developers.
When phase is the project at it’s highest risk of failure?
Highest risk during Initiation and planning phase(early in project). Key decisions during initiation have far reaching implications later in project.
* Initation(beginning of project): High Level of Uncertainty because project scope, objectives, and requirements are not clearly defined yet.
* SH Alignment: Must be aligned and have shared understanding before begin project. Big risk later.
* Resource allocation: Decisions about resources, budget and timeline are made based on limited info, increasing potential inaccuracy and miscalculations.
When is the cost of change highest in project?
More difficult and expensive to make changes later in project as it progresses,
* Accumulated work and interdependencies.
* PMs need robust change mgmt to minimize impact of changes, especially later in project
* Changes later in the project can have a negative effect on quality and integration of the deliverables. Lots of rework.
Each team has their own Scrum master, and we need to know how much work is flowing through each team, and if there’s any blockers or issues. What next?
A. Raise Query at SoS, so each team knows what to do
B. Review Teams Velocity charts
Reviewing Team velocity chart will show how much work(SPs) being done per sprint, and if drop in the trend we know theirs blockers.
Is Optimism apart of Self Regulation or Emotional Intelligence?
Optimism: Is not a form of self regulation, but another skill of emotional intelligence.
· Optimism, on the other hand, is a component of motivation.
· It involves having a positive outlook and expectation of favorable outcomes.
· While optimism is an important trait in emotional intelligence, it is not directly related to self-regulation, which is more about managing and controlling emotions rather than maintaining a positive outlook.
Issue: Which describes your ability to understand and or perceive the emotions of other?
a. Social Awareness?
b. Emotional Intelligence?
c. Social Skill?
Social Awareness? Ans
Emotional Intelligence?- No
Social Skill?- No
Social Awareness: Component of emotional intelligence and involves the a
You are a PO in an Agile team and have a list of features in the backlog that need to be developed.
* Each Feature is assigned a Dollars value, representing return on investment(ROI).
* You would like it to be a risk adjusted BL.
What will you do next?
A. Note the risk impacts in dollars against the return in dollars, then reprioritize the backlog.
C. Capture known risks for each feature, the place cards to control those risks and prioritize in the BL.
XA. Note the risk impacts in dollars against the return in dollars, then reprioritize the backlog.
Y C. Capture known risks for each feature, the place cards to control those risks and prioritize in the BL.
Prioritized PBL tha takes into acco
CGPT: Process For Risk Adjusted BL?
Prioritized PBL tha takes into account not only value and effort of the BL items, but also the risks associated w/ them.
* This approach ensures the team addresses high-risk items early, thereby mitigating potential problems that could impact projects success
What’s the difference between Agile Manifesto and Agile Principles
Agile manifesto is Comparing pred vs agile: Like Individuals and interactions OVER Process and Tools
* 12 Clarifying principles doesn’t compare anything they’re more like just general rules/guidelines.
* Rule 8. Agile processes promote sustainable development. The sponsors, devs, and users should be able to maintain constant pace indefinitely.
Which Agile principles is about Quality?
Continuous Attention to Technical Excelllence and good design enhances Quality
The following sound like Agile Principle but they’re not
* Quality is everyone responsibility.
* Testing done at all levels.
* Continuous flow ensures work is done at reasonable pace and (defects are caught.)Wrong
-Ans last bullet: Principle 8: Maintain sustainable pace indefinitley
Procurment Contracts
PM making list of project closure steps.
What does PM do in regards to contracts w/ 3rd party vendors?
A. Final Inspection of Deliverables
B. Issue formal written notice of project completion to all contractors.
In Control Procurements: This is where we close out our contracts and inspect deliverables.
*But also made sure done by Project close phase.
To Officially close a CONTRACT:
* Must send a formal written notice of the project completion.
* Doing a Final inspection is important for closing procurements, but Official written notice is what’s primarily required to close contract
Get answer later- Activity slides 2-9 Manage Suppliers and Contracts.
You’ll rent 3 monitors(procurement). Which document should you prepare first?
a. Procurement Management Plan
b. Procurement SOW
Notes slide: 17
??
Simplify more.
What’s the difference between Procurement Strategy and Procurement Management Plan?
Procurement Strategy
* Purpose: Provides high level plan for how procurement will be conducted to achieve projects objectives. It defines the approach and methods to be used for acquiring goods and services
* Focuses on the “What” and “Why” of procurement, providing a strategic direction and framework for procurement activities.
* Key Comps:
-Objectives: Defines goals of procurement effort, such as cost savings, quality, timely delivery and risk mitigation.
-Market Anaysis: Analyze market conditions, potential suppliers, market trends, pricing structures
-Procurement Approach: Describes overal procurement approach, such as competitive bidding, direct sourcing, or strategic partners
-Contracting Strategy: Details types of contracts that will be used and rationale behind them.
-Supplier Selection Criteria: Establishes criteria for selecting suppliers, including cost, quality, delivery time, and technical capability.
-Risk Mgmt: ID procurement related risks, and outlines strategies to mitigate them.
-Perf Metrics: Defines how supplier and proc process efficiency measured.
-Implementation Plan: High level timeline and steps for implementing procur strategy.
-Compliance: Ensures proc approach complies to laws/regs.
Procurement Management Plan
* Purpose: Outlines how procurement process will be managed from developing procurement documents through contract closure. Ensuring clear structured approach to managing proc activities.
* Process Overview: Describes the entire process, including how proc activities will be planned, executed, and controlled.
* Roles/Resp: Defines R/Rs fo project team and SHs involved in proc activities.
* Proc Documentation: Lists of documents required for procurement(RFP, RFQ, RFI ), Bid Docs (RFP), Invitation for Bid, contracts, POs
* Vendor Mgmt: Details how vendors will be managed, including vendor selection, evaluation criteria, and performance monitoring
* Contract Type: Types of contracts to be used(FFP, T&Ms..)
* Proc Risk Mgmt: Outlines potential proc risks, and mitigation strategies.
* Proc Sched: Provides timeline for proc activities, inlcuding key milestones and deadlines.
-Ex: Issue RFP in 1 month
-Ex: Complete vendor evaluation in within 3 months.
-Finalize contracts in 4 months
-Begin project execution in 5 months, w/ regulate progresses reviews.
* Make or Buy Analysis: Discusses weather proj work will be done internally or ext.
* Legal and Compliance: Ensures compliance w/ legal regulation
* Budget and Cost Mgmt: Outlines budget for Proc activities and how costs will be managed.
What are 5 conditions a contrat needs to be legal?
Contract consists of: Offer, Acceptance, Consideration, Capacity(legal), Legal Acceptance
- There must be an offer: An Offer and an acceptance of that Offer are required.
- There must be consideration: An exchange is required(usually goods for money).
- Seller offers goods/services for money
3.There must be Legal Capacity: Those entering the contract must be legally able to do so.
- Toddler can’t accidently buy something expensive.
-Manager can’t sign contract past a certain threshold or goes up the chain for approval.
4.There must be legal purpose: The contract must be for something legal.
- Subject of the contract needs to comply with the law. Can’t contract someone to steal for you or do something illegal.
5.There must be intention: Both sides should know it’s legally binding.
- Both parties need to know that the contract is legally binding, and can go to court if not met.
slide 22
When should the assumptions made about a phase be verified?
a. At the beginning of a phase
b. At the end of the project
c. At the beginning of the next phase(ANS)
d. Continually throughout the project
a. At the beginning of a phase
b. At the end of the project
c. At the beginning of the next phase(ANS)
d. Continually throughout the project
C. Beginning of next phase
In project management, particularly in phase-based projects, it is crucial to verify assumptions at the beginning of the next phase. This timing ensures that any assumptions made during the planning and execution of the previous phase are still valid and applicable before proceeding with the new phase’s activities. This verification step is part of the phase review process, often referred to as a phase gate or stage gate, and is essential to manage risks and ensure that the project is on track.
pmbok: End of phase, we review all the work that happened prior to it
The answers in question don’t say end of phase, so right after is the beginning of next phase.
- Assumptions Review: Assumptions made earlier in project reviewed and verified to ensure still valid and applicable.
- Review assumptions from start of project and during previous phases
- Check Assumptions correct, still relevant to current project phase
- Assumptions validated against current project data
Ex: Planning Phase Assumps: Resource availability is confirmed, or alternative resources are identified if initial assumptions are incorrect.
* Closing Phase: Final review of all assumptions captured in LL
* Document which assumps held true and which didn’t, to inform future projects.
What is an Adhoc Request?
Last minute request, not part of plan.
Project is exerpiencing long delays waiting for approvals and getting requirements and acceptance criteria approvals, now there are fewer US appearing in SBL.
How should we tailor the project for this?
PMBOK: Tailoring suggestion is to streamline decisions through fewer people authorized up to a certain value threshold. PO/Sponsor
Stakeholdrs seem engaged, but frequent changes to scope and requirements, causing delays. Issues are often raised and result in multiple rounds of feedback. Not sure what issue could be.
What do you do next?
A. Perform RCA w/ project team to brainstorm ideas.
C. Review issue log, Risk Register, change log for most frequent requestors, then update your SH Engagement Approach for those people.
XA. Perform RCA w/ project team to brainstorm ideas.
* Test tip said if theres confusion do RCA. But that’s just a guideline.
Y C. Review issue log, Risk Register, change log for most frequent requestors, then update your SH Engagement Approach for those people.
* Explanation: A significant number of changes to requirements or Scope may indicate SHs are not engaged or aligned w/ project objectives.
A Project is kicked off due to recent gov inquiry into industry. Which found multiple processes w/ significant regulatory oversight that need to change. The inquiry ordering these changes has given a 10 month deadline before you get penalties. What will you do next?
A. Agile dev approach to deliver change quickly as possible.
B. Proceed, with a Hybrid approach to respond to changes while planning up front.
C. Predictive Approach to ensure quality control
D. Iterative to improve user feedback?
A. Agile dev approach to deliver change quickly as possible.
B. Proceed, with a Hybrid approach to respond to changes while planning up front.
C. Predictive Approach to ensure quality control
D. Iterative to improve user feedback?
Exp C: Significant regulatory oversight may need predictive approach due to:
Required Processes, Documentation, and Demonstration needs.
What required processes?
What Demos? Sounds like agile
PMBOK p.40. “Considerations for selecting a development approach”
You are working on a project w/ a vendor with lots of ambiguity and multiple options team could go with. Many outcomes are possible that have varying degree of impact to improve the situation.
What next?
A. Use experiments and prototypes, and progressive elaboration to work your way through it.
B. Ask team for additional reporting around the diff options so you can make an informed decision.
X-B Ask team for additional reporting around the diff options so you can make an informed decision.
Y-A. Use experiments and prototypes, and progressive elaboration to work your way through it.
Exp-A: 2 types of Ambiguity
Conceptual: Hard to understand.
Situational: Where there’s multiple options and outcomes.
Use progressive elaboration, experiments, and prototypes to work through ambiguity.
What do you need in order to kick off project?
a. Feasibility Study
b. Business Case
c. Project Charter
Project Charter(always go with charter)
E.2 Q.192
Joined org w/ directive PMO, not sure what to expect. What next?
a. Await to be assigned to probject by pmo
b. Review Proj mgmt frameworks templates, tools mandated by PMO
Ans: Await Assigned project by PMO
* Reviewing frameworks and templates is more relevant after being assigned to a project.
* Learning information only useful if your about to apply it, not before.
* First action is to integrate into the new org and PMO by awaiting assignment. Once assigned, reviewing the mandated frameworks and tools will be essential follow-up step, but not an immediate action.
Your agile project has recently had multiple quality issues. Project features have been prioritized by the Product Owner, and broken down into user stories. What will you do to help reduce the cost of quality issues the most?
A. Quality test each US according to it’s Acc.Crit before Release.
B. Ensure a Triad of developer, tester, and customer is involved during the requirements and design.
Ans: B
Explanation: This question is about the Cost of Change. The cost is least during requirements and design, is 20x during build, 50x during test, and 150x if a defect has to be rectified in production. If the requirements, design, and acceptance criteria is incorrect, extra quality testing will not help. (PMBOK Guide) – Seventh Edition, 2021, p90, “Cost of Change”
You are working on a project to build a new customer database system for an engineering team. in working with the requirements, you relise that this system can also work with other teams within your org, and the effort to add those team is quite small. What will you do next?
a. Work w/ the other teams and their managers to escalate the opportunity.
b. Work with those other teams and their managers to exploit the opportunity.
c. Work with those other teams and their managers to enhance the opportunity.
d. Work with the other teams and their managers to accept the opportunity.
Ans: A.
- Share? Not an option
- Exploit: Add resources to make it happen.
- Exploit vs Enhance
- Enhance: Increase
- Escalate: Is it beyond PM authority?