sepC

highest priority

even late in development. Agile processes harness change for the customer's competitive advantage.

from a couple of weeks to a couple of months, with a preference to the shorter timescale. 

asdf

SCRUM is an agile, lightweight process for managing and controlling software and product development in changing environments. 

• Self-organizing teams
• Product progresses in a series of one- to four-week “sprints”
• Requirements are captured as items in a list of a “product backlog”
• No specific engineering practices prescribed
• Uses generative rules to create an agile environment for delivering projects 

• Scrum projects make progress in a series of “sprints”
• Typical duration is 2–4 weeks or a calendar month at most
• A constant duration leads to a better rhythm
• Product is designed, coded, and tested during the sprint 

• Core Roles
  • Product Owner
  • Scrum Master
  • ScrumTeam
• Other Roles
  • Users
  • Management
  • other Stakeholders 

• Define the features of the product
• Decide on release date and content
• Be responsible for the profitability of the product (ROI)
• Prioritize features according to market value
• Adjust features and priority every iteration, as needed
• Accept or reject work results 

• Represents management to the project
• Responsible for enacting Scrum values and practices
• Removes impediments
• Ensure that the team is fully functional and productive
• Enable close cooperation across all roles and functions
• Shield the team from external interferences 

• Builds the product that the Product Owner indicates
• To deliver the potentially shippable product each Sprint
• A very high degree of autonomy and accountability.
• The Team decides what to commit to, and how best to accomplish that commitment;
• Typically 5-9 people
• Cross-functional, i.e. Programmers, testers, user experience designers, etc.
• Teams are self-organizing
• Membership should change only between sprints 

• Core Activities
  • Sprint Planning
  • Sprint Review
  • Sprint Retrospective
  • Daily Scrum
• Other Activities
  • „Sprint 0“
  • Develop
  • Discuss 

• Team selects items from the product backlog they can commit to completing
• Sprint backlog is created
  • Tasks are identified and each is estimated (1-16 hours)
  • Collaboratively, not done alone by the Scrum Master
• High-level design is considered

• Parameters
  • Daily
  • 15-minutes
  • Stand-up
• Not for problem solving
  • Whole world is Invited
  • Only “pigs” can talk
  • Helps avoid other unnecessary meetings 

• Team presents what it accomplished during the sprint
• Typically takes the form of a demo of new features or underlying architecture
• Informal
  • 2-hour prep time rule
  • No slides
• Whole team participates
• Invite the world
• Onle “Done’s” are presented 

• Periodically take a look at what is and is not working
• Typically15–30 minutes
• Done after every sprint
• Whole team participates
  • Scrum Master
  • Product owner
  • Team
  • Possibly customers and others
• For example
  • “Start / Stop / Continue”
  • “Good / Could be better/ Measures” 

• Core Artifacts
  • Product Backlog
  • SprintBacklog
  • Burndown Charts
• Other Artifacts
  • Product
  • Impediment Backlog