SCRUM

Question 1

Define SCRUM as a methodology

Answer 1

Agile method that focuses on managing iterative development rather than specific agile practices

Question 2

Phase 1 of SCRUM?

Answer 2

Initial Phase: outline planning phase where you establish general objectives for the project and design the software architecture

Question 3

Phase 2 of SCRUM?

Answer 3

Sprint Cycles: Where each cycle develops an increment of the system

Question 4

Phase 3 of SCRUM

Answer 4

Project Closure Phase: wraps up the project, completes required documentation such as system help frames and user manuals, and assesses the lessons learned from the project

Question 5

Define Product, Product Owner and Product Backlog in SCRUM

Answer 5

1. Product: Software being developed by Scrum Team
2. Product Owner: A team member who is responsible for identifying product features and attributes. They review work done and help to test the product
3. Product Backlogs: List of what needs to be done to complete the product, items in list PBI (Product backlog items)

Question 6

Define Sprint, Scrum and Scrum Master in SCRUM:

Answer 6

1. Sprint: a short period, typically two to four weeks, when a product increment is developed
2. Scrum: A daily team meeting where progress is reviewed and work to be done that day as discussed and agreed
3. Scrum Master: A team coach who guides the team in the effective use of SCRUM

Question 7

Define Velocity in SCRUM:

Answer 7

Velocity: An estimate of how much work a team can do in a single sprint

Question 8

What is ready for consideration?

Answer 8

High-level ideas and feature descriptions that will be considered for inclusion in the product. Tentative, may change or not be included in the final product.

Question 9

What is ready for refinement?

Answer 9

The team has agreed that this is an important item that should be implemented as part of the current development. Reasonably clear definition of what is required, work is needed to understand and refine the item.

Question 10

What is ready for implementation?

Answer 10

The PBI has enough detail for the team to estimate the effort involved and to implement the item, dependencies on other items have been identified.

Question 11

PBI Estimation Metrics:

Answer 11

1. Effort Required: Expressed in person-hours or person-days. This is not the same as calendar time. Several people may work on an item, which may shorten the calendar time required.
2. Story Points: Arbitrary estimate of the effort involved in implementing a PBI, taking into account the size of the task its complexity, the technology that may be required, and the ‘unknown’ characteristic of the work

Question 12

How are story points estimated?

Answer 12

Story points are estimated relatively. The team agrees on the story points for a baseline task and other tasks are estimated by comparison.

Question 13

Features of Extreme Programming:

Answer 13

1. New versions may be built several times a day
2. Increments delivered to customers every 2 weeks
3. All tests must be run for every build and the build is only accepted if all tests pass

Question 14

Define Small Releases:

Answer 14

Minimal set of features and requirements that provides business value are created first

Question 15

Define Simple Design:

Answer 15

Design meets current requirements and nothing more

Question 16

Define Collective Ownership:

Answer 16

Pairs develop everything and take complete ownership of all code

Question 17

Define Sustainable Pace:

Answer 17

Large amounts of overtime are not considered acceptable

Question 18

Define On-site customer:

Answer 18

End-user that is available full time, in XP they are apart of the team

Question 19

XP Testing

Answer 19

Test-first development, the program is tested after every change, user involved in development and testing

Question 20

Problems with test-first development:

Answer 20

Developer prefer to code over the test and will take shortcuts that miss testing a few things

Question 21

Problems with Agile:

Answer 21

1. Incompatible with legal approaches to contracts like big companies (payment for features bad for the developer, pay hourly is bad for the company)
2. For new software, not software management
3. For small co-located teams

Question 22

How does Agile work for large systems?

Answer 22

1. Teams develop each part of the system separately

2. Large systems are brownfield systems (include and interact with existing systems)