L2: Moving Through Software Development

Question 1

Waterfall

Answer 1

• Traditional engineering perspective
• Feasible for clear/static requirements
• Clear phase distinction is not realistic

Question 2

V-Model

Answer 2

• Extension of the Waterfall
• Focus on testing and validation
• Widely used

Question 3

Waterfall & V-Model: Analysis

Answer 3

Positives:
* Simple
* Specifications/deliverables fully defined beforehand

Negatives:
* Assume frozen requirements
* Deliver whole system at once
* Fixed linear process
* Extensive documentation

Question 4

Prototyping

Answer 4

• Often integrated in other processes
• Develop prototype for feedback
• Refine prototype iteratively

Question 5

Prototyping: Analysis

Answer 5

Positives:
- Identify problems fast
- Faster customer feedback
- Gather information about the software

Negatives:
- Potentially excessive testing of prototypes by customer
- Mismatch and changing customer requirements
- Budgeting more challenging

Question 6

Spiral

Answer 6

• Integrates previous models:
  1. One loop is a waterfall
  2. Each loop leads to a prototype
• Emphasize managing costs and risks
• Exact number of loops can vary

Question 7

Spiral: Analysis

Answer 7

Positives:
- Integrates risk management
- Considers changes to requirements explicitly
- Emphasizes communication, customer satisfacion, and flexibility

Negatives:
- Complex
- Expensive / resource intensive
- Challenging risk and time management

Question 8

“traditional” processes

Answer 8

Pros:
- Structure process/methodology as a guide
- Proven successful in the past
- Clearly defined requirements
- Extensive quality control

Weaknessees:
- Slow and inflexible
- Typically, high costs
- Limited customer involvement

Question 9

Core values of the agile manifesto

Answer 9

• Individuals and interactions
• Working software
• Customer collaboration
• Responding to change

Question 10

Emphasis of the agile manifesto

Answer 10

• Having people with the right competencies work together
• Delivering the intended software
• Working with the customer to understand/explore their demands
• Being flexible to react to changes in the project

Question 11

Agile: Analysis

Answer 11

Positives:
- Flexible
- Customer involvement
- Continuous delivery
- Collaboration
- Early/frequent testing

Negatives:
- Predictability?
- Abandoned documentation?
- Lack of planning?
- Time and resource demands?

Question 12

What is a “Sprint?”

Answer 12

• Structures all other activities
• Fixed period of time for working
• After each Sprint, a new one starts
• After each Sprint, an increment exists

Question 13

Daily Scrum

Answer 13

• Meeting with all developers
• Inspect progress
• Plan next day

Question 14

Sprint Review

Answer 14

• Inspection of the Sprint
• Presentation to customer

Question 15

Sprint Retrospective

Answer 15

• Improving quality and effectiveness
• Resolving problems

Question 16

Roles in SCRUM

Answer 16

• Product Onwer: Responsible for product backlog
• Scrum Master: Responsible for implementing Scrum
• Developers: Creating increment

Question 17

Definition of Ready

Answer 17

Defines when an item in the Product Backlog is ready to be worked on:
- Clear and concise writing
- Acceptance criteria are defined and testable
- Dependencies have been identified and addressed
- The stakeholders have approved the item
- The team has the skills needed to complete the item
- All resources needed are available

Question 18

Definition of Done

Answer 18

Defines the criteria for an iutem to be considered complete
- Fully reviewed by another developer
- Has been tested without errors
- Passed continuous integration
- Documentation is updated
- Approved by customer

A done Backlog Item results in an increment

Question 19

Scrum: Analysis

Answer 19

Positives:
- Structure for dividing tasks
- Fast forwards moving
- Continuous meetings and clear roles
- Customer involvement
- Working prototypes

Negatives:
- Scope creep
- Requires experience to implement
- Keeping time management and motivation