POM E3

Question 1

Product Backlog :

Answer 1

List of requirements for the whole product

Question 2

Sprint Backlog:

Answer 2

List of requirements and tasks for one iteration (“Sprint”)

Question 3

Potentially Shippable Product Increment:

Answer 3

Release to the Product Owner that

contains all results of the current Sprint

Question 4

Scrum Meetings, contains :

Answer 4

Project Kickoff Meeting (Start of the Project): Create and prioritize Product Backlog

#Sprint Planning Meeting (Start of each Sprint): Create Sprint Backlog
# Daily Scrum Meeting (Every Morning,15min): Standup meeting to share status,
impediments and promises
#Sprint Review Meeting (End of each Sprint): Demonstration of realized backlog items
to the Product Owner (and other stakeholders)

Question 5

Scrum-Team, Product owner ;

Answer 5

Defines the product

Responsible for results

Question 6

Scrum-Team, Scrum Master;

Answer 6

Resolves impediments

Responsible for the process

Question 7

Scrum-Team, Development team;

Answer 7

Self-organizing and cross-functional

Realizes the product increment

Question 8

What is a Sprint?

Answer 8

# Typically 2-4 weeks long 
# Starts with Sprint Planning Meeting (Create the Sprint Backlog,  Development Team and Product Owner select the items together)

Ends with Sprint Review Meeting (product increment, Demo of the application during the meeting, Product Owner gives feedback)

Question 9

The development team during a sprint

Answer 9

# Works on the items in the Sprint Backlog
# Uses e.g. a Task Board to visualize the status of these items
# The Scrum Master visualizes the progress, e.g. in a Burn Down Chart
(Items, TODO, in progress, in review, Done)

Question 10

Product backlog

Answer 10

• Collection of items (e.g. user stories, scenarios, etc.) prioritized by the Product
Owner
• changeable and reprioritizeable
• Created before the project starts and based on kickoff meeting

Question 11

Priorities, and by whom is it done?

Answer 11

Prio 1 = Critical
(released in product increment 1)

Prio 2 = Major
can be realised after first release)

Prio 3 = Minor
(if there is time we’ll do it)

Prio 4 = Trivial
(may be realised)

Prioritization is done by the Product Owner

Question 12

Two ways to control Software Development

Answer 12

• Organizational Maturity

- Agility

Question 13

Empirical Process Control Model, and when to apply it

Answer 13

# Empirical process: An imperfectly defined process, not all pieces of work are completely understood
# Deviations, errors and failures are seen as opportunities that need to be investigated (the unexpected is expected)
# Control and risk management is exercised through frequent inspection 

The EPCM pre conditions:
# Change is frequent and cannot be ignored
# Change of requirements, change of technology, change in the organization, people
change too.

Question 14

User stories

Answer 14

Includes a sentence that the describes what the user does or needs.
US is ofter written on a card.

Question 15

Properties of a good User Story: INVEST

Answer 15

Independent (avoid overlapping)
Negotiable (a basis for discussion between dev. team and product owner)
Valuable and Vertical (features not layers are planned and developed)
Estimable (basis of the project plan is the product backlog)
Small
Testable

Question 16

What are Scenarios ?

Answer 16

A scenario represents a concrete sequence of

interactions between one or more actors and the system.

Question 17

What is the relation between User Stories, Use Cases and Scenarios ?

Answer 17

#Scenarios are typically created during Analysis
#Use Cases and Scenarios typically cover a larger scope and are more
formal than User Stories 
# User Stories are usually created during requirements elicitation

Question 18

What is a task ?

Answer 18

Smallest unit of work.

Question 19

Software Project

Answer 19

#A software project has a specific duration, schedule, 
consumes resources and produces work products

Question 20

What are Management activities to complete a software

project ?

Answer 20

Tasks, activities, project functions

Question 21

What is Software Project Management Plan (SPMP) ?

Answer 21

The controlling planning document for a software

project
#Specifies the technical and managerial approaches
to develop the software product
#May be part of the agreement

Question 22

What is Project Agreement and what does it include ?

Answer 22

A document written for a client that
defines:
• the scope, duration, cost and deliverables for the project
• the exact items, quantities, delivery dates, delivery location

Question 23

What is IEEE Std 1058 and what does it ?

Answer 23

The IEEE 1058 standard describes the structure of a
software project management plan.
Specifies the format and contents of software project
management plans but not the procedure

Question 24

WBS

Answer 24

Hierarchical decomposition of the project into
activities and tasks. (The aggregation of all the work
to be performed in a project. )

Question 25

Two major philosophies for Creating Work Breakdown Structures

Answer 25

#Activity Orientend
#Object oriented

Question 26

Approaches to Develop a WBS

Answer 26

Product component approach

• Structure the work around the work products
• Example: Design documents, manuals, delivered system
#Functional approach
• Structure the work around development activities
• Example: Analysis, design, implementation, integration
#Geographical area approach
• Structure the work based on the geographical location
• Example: Munich team, off-shore team
#Organizational approach
• Structure the work based on the organization
• Example: Line organization with R&D, predevelopment,
product development, marketing, sales.
#Agile approach
• Structure the work as a to-do list
• Example: Product backlog, sprint backlog.

Question 27

When to use what Approach

Answer 27

The teams are distributed over the continent:

• Geographical area approach
# The teams consist of experienced developers:
• Product component or agile approach
#The project consists mostly of beginners or has an
inexperienced project manager:
• Functional approach
#The project is a continuation of a previously successful
project, there are no changes in the requirements and no
new technology enablers:
• Organizational approach

Question 28

Displaying Work Breakdown Structures (3 formats)

Answer 28

Organization-chart format

• Effectively portrays an overview of your project and the
hierarchical relationships of different activities and tasks
#Outline format
• Sub-activities and tasks are indented below activities
• Backlog: Outline format without indentation.
#Bubble format
• The bubble in the center represents your project
• Lines from the center bubble lead to activities
• Lines from activities lead to tasks.

Question 29

What are Two useful States in large Projects

Answer 29

#initial Planning 
#Project initiation