Key Terms

Question 1

WBS - Work Breakdown Structure

Answer 1

WBS is hierarchial and breaks down the work and it’s deliverable oriented. It defines the work of the project

Question 2

Milestone

Answer 2

A significant point in time or event on schedule (black diamond) – when you hit it, celebrate!

Question 3

Baseline

Answer 3

Where a project can become a failed project or successful. It’s an approved project (baseline) that includes the project schedule

Question 4

Triple Constraint

Answer 4

Triangle that balances the Time, Money, Scope typically around changes [Quality in the middle]

Question 5

Project Life Cycle

Answer 5

Single phase project: Initiating, Planning, (Monitoring & Controlling), Executing, Closing

Question 6

Gantt Chart

Answer 6

Graphical display of schedule information that includes dates, duration, owners, and deliverable

Question 7

CCB - Change Control Board

Answer 7

A group of stakeholders (representative from stakeholder groups) that are on the board and people designated in the project plan who are the people with the authority to make approval or denies. Review/approve/reject/delay changes.

Question 8

Stakeholders

Answer 8

Include people, customers, organizations, vendor partners, that are actively involved in the project. They may be affected positively or negatively by the outcome of the project so they have vested interest in the outcome

Question 9

Change Management

Answer 9

Project management plan (who, what, where) related to changes in the project in order to control the scope

Question 10

Risk Mitigation

Answer 10

About building a risk response planning technique associated with threats to the project. If something occurs, identify what happens next?&raquo_space; Goal is to reduce probability of occurrence or impact

Question 11

RAG Status - Red, Amber, Green

Answer 11

Tool to indicate whether something is on or off track

Question 12

PI - Product Increment

Answer 12

Additional functionality to be added at each sprint/iteration

Question 13

Safe Agile

Answer 13

Brings various functional groups together to plan & deliver a bigger working software for each sprint/iteration

Question 14

WS - Working Software

Answer 14

Software that is built with MVP to make it functional to the customer

Question 15

MVP - Minimum Viable Product

Answer 15

What are the minimum functionalities to make the software usable for the customer

Question 16

Functional Requirement

Answer 16

A requirement that essentially specifies something the system should do (business rules, transaction corrections, adjustments, cancellations, audit tracking, historical data)

Question 17

Non-Functional Requirement

Answer 17

Non-functional requirements describe how the system works, while functional requirements describe what the system should do

Question 18

Non-Functional Requirements v2

Answer 18

Requirement that describes how the system should behave and that it is a constraint upon the systems behavior “a hat must not break under pressure of less than 1000 psi” — (performance, capacity, security, usability, availability, reliability)

Question 19

Safe Agile

Answer 19

Team, Program, Portfolio Management

Question 20

Scrum Mechanism

Answer 20

2 week iterations. Each Sprint starts with:

 1. Planning (decide what user stories to be delivered)
 2. Daily meetings to ensure progress
 3. At the end, DEMO to see functionality work
 4. Retrospective meeting to get lessons learned

Question 21

SCRUM

Answer 21

Scrum is a framework for Teams to get work done.