scrum

Question 1

Extreme Programming (XP)

Answer 1

• Perhaps the best-known and most widely used agile method
• XP takes an ‘extreme’ approach to iterative development
  
  • New versions may be built several times per day
  • Increments are delivered to customers every 2 weeks
  • All tests must be run for every build and the build is only accepted if tests run successfully

Question 2

XP & Agile

Answer 2

• Incremental development is supported through small, frequent system releases.
• Customer involvement means full-time customer engagement with the team
• Change supported through regular software releases
• Maintaining simplicity through constant refactoring of code
• XP Release Cycle

Question 3

XP release cycle

Answer 3

select user stories for release
break down stories to tasks
plan release
develop/integrate/test software
release software
evaluate system

Question 4

XP Practices

Answer 4

incremental planning
small releases
simple design
test-first development
refactoring
pair programming
collective ownership
continuous integration
sustainable pace
on-site customer

Question 5

SCRUM

Answer 5

1. outline planning and architectural design
2. sprint cycle: asses, select, review, develop
3. project closure

Question 6

Scrum roles

Answer 6

Product Owner, Scrum Master, Developers

Question 7

Scrum artifacts

Answer 7

Product Backlog, Sprint Backlog, Increment

Question 8

Scrum events

Answer 8

Sprint, Sprint planning, Daily goal, Sprint goal, Sprint review, Sprint retrospective

Question 9

Scrum Master

Answer 9

• arranges daily meetings
• tracks the backlog of work to be done
• records decisions
• measures progress against the backlog
• communicates with customers and management outside of the team

Question 10

Scrum Benefits

Answer 10

• The product is broken down into a set of manageable and understandable chunks
• Unstable requirements do not hold up progress
• The whole team have visibility of everything and consequently team communication is improved
• Customers see on-time delivery of increments and gain feedback on how the product works.
• Trust between customers and developers is established and a positive culture is created in which everyone expects the project to succeed.