User Stories
Velocity
Agile Retrospectives
Scrum
Core Scrum roles (taken from http://en.wikipedia.org/wiki/Scrum_%28development%29 )
The core roles in Scrum teams are those committed to the project in
the Scrum process—they are the ones producing the product (objective of
the project).
- Product Owner
- The Product Owner represents the voice of the customer
and is accountable for ensuring that the Team delivers value to the
business. The Product Owner writes customer-centric items (typically user stories), prioritizes them, and adds them to the product backlog.
Scrum teams should have one Product Owner, and while they may also be a
member of the Development Team, it is recommended that this role not be
combined with that of ScrumMaster.[8]
- Team
- The Team is responsible for delivering the product. A Team is
typically made up of 5–9 people with cross-functional skills who do the
actual work (analyse, design, develop, test, technical communication,
document, etc.). It is recommended that the Team be self-organizing and
self-led, but often work with some form of project or team management.
- ScrumMaster
- Scrum is facilitated by a ScrumMaster, also written as Scrum Master,
who is accountable for removing impediments to the ability of the team
to deliver the sprint goal/deliverables. The ScrumMaster is not the team
leader but acts as a buffer between the team and any distracting
influences. The ScrumMaster ensures that the Scrum process is used as
intended. The ScrumMaster is the enforcer of rules. A key part of the
ScrumMaster’s role is to protect the team and keep them focused on the
tasks at hand. The role has also been referred to as servant-leader to reinforce these dual perspectives.
Nice interesting presentation from folks at Google on Agile testing Extract from this presentation | Item | Traditional Testing
| Agile Testing
| | Change | Manage and Control It
| Accept It
| | Planning | Comprehensive Test plan up front
| Design as you go
| | Handoffs | Formal Entrance and exit criteria
| Not a rally race, collaborate
| | Automation | System level built by cool specialists, created after the code is done
| All levels, built by everyone
|
|
|