Module 3: Managing Our Projects: Tools, Best Practices, and Agile 🤸🏻‍♀️ Flashcards

1
Q

Project Constraints

A

limiting factor that affects the execution of a project, program, portfolio, or process.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Artifacts

A

ANY documents and records related to your project; serve as evidence of the project’s planning, execution, and completion

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Project Documents

A

refer to all of the different documents used to initiate, plan, execute, monitor and control, and close the project thatDO NOTinclude the items that are apart of your project management plan

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

PMIS

A

tools that help track and manage your project - think PM software + file repositories + any shared drives

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Data Gathering

A

involves collecting information, a crucial tool in project planning and execution

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Data Analysis

A

aiming to make informed decisions and drive the project forward

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Alternative analysis

A

The evaluation of the different choices available to achieve a particular project management objective. It is an analytical comparison of different factors

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Cost benefit analysis

A

Cost of the proposed actions and the consideration of the benefits the actions will create!

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Root cause/causal analysis

A

Determine what activities, people, organizational processes, or other factors are contributing to an effect - fishbone diagrams or ishikawa are good examples of root cause diagrams.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Trend analysis

A

Analyzing recurring problems, threats and opportunities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Variance analysis

A

Differences in planned vs experienced; budget assessment

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Data Representation

A

transforms collected data into visual formats, such as line graphs or diagrams.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Work Performance Data

A

raw information collected during project execution

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Ways of Working

A

emphasizing diverse disciples and practices to ensure versatility in project execution

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Power Skills

A

focusing on essential skills such as team collaboration, conflict resolution, motivation, and effective communication

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Business Acumen

A

Highlighting the significance of understanding and aligning projects with organizational goals and strategies

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

INITIATING

A

The project or phase will get authorization to start. Initiating has 2 processes. It is the smallest of the process groups. The project charter and stakeholder register are the main outputs.

Authorize the project to get started
Assign project manager
Identify stakeholders
Determine business case, objectives, why is the project needed?
Identify very high level estimates for time and costs
Determine high level risks that can affect the project schedule or budget
Identify high level assumptions an constraints

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

PLANNING

A

Iterative and ongoing processes to establish the total scope of effort, to define objective, and identify the course of action required to attain those objectives. Main output is creation of the project plan which includes many different planning documents.

Create the project management plan and all of it’s subsidiary plans
Collect requirements from stakeholders
Create and plan out scope, cost, time (all added into project management plan)
Identify risks and create risk planning to mitigate those risks before they happen
Determine what components need to be obtained from outside vendors (procurement planning)
Plan to meet the quality requirements - what does quality in the project mean? how will that be measured/ tracked/ calculated?
Obtain approval of the project management plan

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

EXECUTING

A

Getting the project work done, acquire and develop your team, and bring the team together to complete your deliverables (work).

Carry out project work according to project plan
IMPLEMENT change requests (corrective and preventative actions as well as defect repairs and other approved changes)
Select and acquire team members
Manage and resolve conflicts among project stakeholders
Manage quality by conducting quality assurance and improving processes
Update project stakeholders on progress through meetings, reports etc
Select vendors and award contracts (procurement)
Engage stakeholders on the project so they are aware and apart of what is happening
Implement the risk responses
Capture and document the lessons learned (Capturing lessons learned is not an activity limited to project closeout.It is a vital action that project teams should continually perform throughout)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

MONITORING AND CONTROLLING

A

There are 12 processes in M&C. M&C ensures that the project stays on track. You must look at the work getting done and compare it to the original plans, ensuring that the project is on budget, schedule, in scope, to verify, review, and compare. In this process group the project manager is taking corrective actions and may need to enter change requests.

Run checks to ensure that the scope, time, and budget of the project is on track
Ensure quality requirements are met
Control risks by performing risk reviews, reassessments, and audits
Manage and evaluate procurements ensuring work they are completing matches SOWs and agreements
Request changes to ensure project is on track, perform integrated change control, Inform stakeholders of change requests, influence factors that affect changes
Ensure stakeholders are actually being engaged as stated in the stakeholder engagement plan
Measure performance against performance measurement baselines
Analyze performance data
Determine if variances require changes
Create forecasts
Get deliverables formally accepted so the project can move towards closing

21
Q

CLOSING:

A

This process group happens after the client or sponsor has accepted the project deliverables. Once deliverables have been accepted, contracts need to be closed out, lessons learned need to be documented and finalized and the completed deliverables need to go through a hand over to project customers, or sponsors.

Confirm work is done and get it accepted by customer/ sponsors
Complete final procurement closure
Archive project documents
Create final reports on the project
Update templates and knowledge basis / PMIS

22
Q

Delphi Technique

A

a project management method that involves consulting a group of experts and using systematic feedback rounds to make decisions about complex issues. The technique is based on the idea that collective wisdom is greater than individual knowledge. It’s also known as the “Wide-band Delphi” technique. Can use this for estimating and quantifying costs and risks.

23
Q

Monte Carlo Simulation

A

a mathematical technique that predicts possible outcomes of an uncertain event. Computer programs use this method to analyze past data and predict a range of future outcomes based on a choice of action.

24
Q

PMI Talent Triangle

A

Business Acumen, Ways of Working, Power Skills

25
Agile
project management approach that prioritizes flexibility, collaboration and customer satisfaction - ensure that higher-level objectives are explained and the team members are empowered to self-organize specific tasks as a group to best meet those objectives - product owner prioritizes the product backlog. NOT THE PROJECT MANAGER. - combination of Iterative (where we gather feedback to improve) and Incremental project lifecycles (where we deliver smaller usable features of value to our customer)
26
4 Values of Agile Manifests
1. Individuals and interactions over processes and tools 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. Responding to change over following a plan
27
Product Owner
Knows the software product inside out, has control over the product roadmap, and owns the product backlog, represent the customer. Works closely w/product manager. Answers questions, prepares stories.
28
Product Backlog
A dynamic document that outlines the tasks the development team plans to complete during the lifetime of the product. It changes over time and the product owner has final say in what makes it onto the product backlog. It is basically a list of things (features, functions) that needs to get done to the product!
29
Stories/ User Stories
Breaking down features into pieces so developers know what is needs to be built, the product owner typically creates user stories alongside technical SMEs
30
Sprint Backlog
This is a subset of the product backlog. We take the most important features and functions from the bigger product backlog (above) and choose what will get done next. A dynamic document that outlines the tasks the development team plans to complete during the current sprint. It is created during the Sprint Planning meeting, where the team decides which items from the Product Backlog (a prioritized list of features and user stories) they will work on during the sprint.
31
Sprint/ Iteration
a time period during which a specific amount of work is completed. Typically, a sprint lasts 2 to 4 weeks. The team commits to delivering a set of features (aka user stories) within this timeframe. We can use Sprint and Iteration interchangeably
32
Product Roadmap
visual representation that outlines the high-level vision and direction for the development of a product over time. It serves as a tool to align stakeholders, such as product managers, development teams, executives, and customers, on the planned features, enhancements, and milestones for the product. A roadmap for what happens next.
33
Daily Standup
A daily meeting to touch base on project status, wins, blockers etc (15 mins or less can be a little more, but it is SHORT).
34
Sprint Review
A review meeting done at the end of the Sprint. The work is demoed to the customer/ stakeholders and they will give their feedback. They will give their input on the features they asked for, and say what looks good and what other feedback they have.
35
Retrospective
meeting to reflect on what went well and what needs improvement. Use this retrospective to learn lessons about what the team did well during development/ during the sprint basically an Agile “Lessons Learned”
36
Team Charter
How the team will communicate, work together, meet the needs of the product and each other, as well as WHO is the team. Roles, responsibilities, and the product owner.
37
MVP (Minimum Viable Product)
a new product with the minimum features necessary to satisfy early customers and collect feedback for future development. The MVP contains the necessary features to actually use the product. The best approach to meet a aggressive timelines is to re-evaluate the scope based on stakeholder value, and focus on the highest priority features that can be delivered within the allotted time, i.e., the concept of Minimum Viable Product (MVP).
38
Product Manager
Very similar to product owner, typically works directly with the customer and then comes to the product owner with guidance.
39
Spikes
Sprints or iterations added to explore a new risk, approach, or technologies
40
Velocity
is the amount of work (measured by points, hours, cards or anything you wish) a team completes on average in a given sprint. By checking the total points for the cards you wish to complete against what is possible via the team velocity, you will know what is possible an adjust as necessary.
41
The Agile Inverted Triangle
focus shifts to delivering value and adapting to change
42
LEAN
- focus on principles guiding Agile - goal: eliminate waste, empower teams, deliver fast, and embrace systems thinking - lean mindset: trust your team to make decisions, delivering as fast as possible, empowering the team
43
KANBAN
- derived from the lean principles, a pull system to product development - core principles: visualize progress, limit work in progress, manage the flow, understand the big picture, and foster collaboration
44
SCRUM
- core concepts: iterative and incremental development, dedicated and cross-functional teams - values: transparency, inspection, adaptation - scrum terms: sprint planning, daily scrum, sprint review, sprint retrospective, backlog refinement
45
Extreme Programming (XP)
- centered around good software development practices - core principles: communication, feedback, courage, respect, simplicity - roles: coach (scrum master), customer (product owner), programmers. testers - practices: planning activities, small releases, metaphors. sustainable pace customer test, pair programming, collective code ownership, continuous integration, refactoring
46
Scaled Agile Framework (SAFe)
focuses on detailing practices, roles and activities at the portfolio, program, and project levels, and focuses on organizing the enterprise around value streams that provide value to the customer. It values: 1. Taking an economic view and apply systems thinking. 2. Visualizing and limiting work in progress (like Kanban) and reducing batch sizes. 3. Build incrementally with fast, integrated learning cycles.
47
Hybrid Project Management
uses a combination of plan driven and agile approaches to managing projects
48