Module 3: Project Initiation

Question 1

When should an Incremental development approach be used

Answer 1

If you are leading a project where requirements are not well defined, change is expected, and the customer wants several deliveries of useful products

Question 2

Which of the following is not an accountable unit in the scrum framework?
Product manager
Scrum master
Development team
Project owner

Answer 2

Product manager

Question 3

Customer request

Answer 3

A description of what a customer or user would want from a product or solution

Question 4

Iterative approach

Answer 4

Used with feedback is needed on a regular basis. Final product not delivered until it has undergone a few iterations.

Question 5

Incremental approach

Answer 5

Builds on previous one. Complete one small part before moving onto next.

Repeats planning and executing for each increment

Question 6

User stories

Answer 6

written in a way to be clear whether the team is using iterative or incremental approach

Question 7

Product lifecycle

Answer 7

include one or more projects that can start at any point during the product life cycle

Question 8

Phases of adaptive/agile development

Answer 8

Start with design phase and includes 3 iterations. Feedback and backlog prioritization is done after each iteration

Question 9

Gate meeting

Answer 9

done prior to each phase to determine whether it should go ahead or not.

Question 10

Scrum

Answer 10

Complex or innovative projects.

To use an analogy, think of Agile as a diet and Scrum as a type of diet

Question 11

Product Backlog

Answer 11

This contains a prioritized list of work that needs to be done.

Question 12

Sprint Backlog

Answer 12

During the planning stage, the project team takes an item from the product backlog and creates the sprint backlog.

Question 13

Sprint

Answer 13

The project team will have 2-4 weeks to complete this work.

Question 14

Daily Scrum Meeting

Answer 14

Each day the project team meets to discuss progress.

Question 15

Scrum Master

Answer 15

A Scrum Master is in charge of these meetings and asks questions like:
1) How much has been done since our last meeting.
2) Have there been any problems/obstacles.
3) What will be done for today

Question 16

Potentially Shippable Product

Answer 16

At the end of the 2-4 weeks the product should be completed and ready for the client’s inspection.

Question 17

Pre-initiating processes

Answer 17

1) approval through a formal selection process.
2) Determine scope, time, and cost constraints for the project.
3) A business case
4) PM selected.
5) The project process and expectations need to be discussed with PM.
6) identify stakeholders
7) create project charter
8) Kick-off meeting

Question 18

Business case components

Answer 18

• Justification for investing
• cost-benefit analysis

Question 19

Components of stakeholder registry

Answer 19

name, position, location, role in project, internal/external, whether they support project or not, requirements.

Question 20

Stakeholder analysis

Answer 20

shows their interest and level of authority

Question 21

Project charter

Answer 21

establishes formal existence of project. High level information
- objectives
-goals
-stakeholders
- constraints
- risks
-budget
Formal authorization to begin project and authority to use resources

Question 22

SOW

Answer 22

statement of work
Identifies business need, scope, organization’s strategic vision, goals, and objectives.

Question 23

Key stakeholders in Agile project

Answer 23

Product Owner (client, manager): Responsible for maximizing the value of the product
Scrum Master (PM): Responsible for promoting and supporting the Scrum process
Development Team: These are the professionals who do the work to complete the deliverables during each sprint.

Question 24

Vision statement

Answer 24

Describes the desired future state that would be achieved by developing and deploying a product.

Question 25

Product Release Plan:

Answer 25

It is a process of deciding which features of the project will be offered in which release.

Question 26

User story

Answer 26

This is a description of what a customer or user would want from a product or solution.
Format: As a < type of user >, I want < some goal > so that < some reason >.

Question 27

Product Backlog:

Answer 27

Product owner creates
-ordered and evolving list of what is needed to improve the product. This list is actually a list of user stories.

Question 28

Product Strategy

Answer 28

high-level plan (roadmap) describes what the organization hopes to accomplish with its product and how it plans to do so. The roadmap contains a prioritization list of business goals.