Scrum

Disponível somente no TrabalhosFeitos
  • Páginas : 12 (2969 palavras )
  • Download(s) : 0
  • Publicado : 22 de abril de 2013
Ler documento completo
Amostra do texto
Guide Scrum

1 - Scrum Framework
- Framework Scrum consist: Team Scrum + roles + events + artifacts + rules
- The rules of Scrum bind together the events, roles, and artifacts, governing the relationships and interection between them.

2 - Scrum Theory

- Empiricism asserts that knowledge comes from experience and making decisions based on what is known
- Three pillars uphold everyimplementation of empirical process control: transparency, inspection, and adaptation.

a) Transparency requires those aspects be defined by a common standard so observers share a common understanding of what is being seen.
> A common language referring to the process must be shared by all participants; and,
> A common definition of “Done” must be shared by those performing thework and those accepting the work product.

b) Scrum users must frequently inspect Scrum artifacts and progress toward a goal to detect undesirable variances.

c) If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted.
> Scrumprescribes four formal opportunities for inspection and adaptation:
- Sprint Planning Meeting
- Daily Scrum
- Sprint Review
- Sprint Retrospective

3 - Scrum

- Scrum is a framework structured to support complex product development.
- Scrum consists of Scrum Teams and their associated roles, events, artifacts, and rules.
- Each component within the framework servesa specific purpose and is essential to Scrum’s success and usage.

4 - Team Scrum (TS)
- The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master.
- Self-organizing: teams choose how best to accomplish their work, rather than being directed by others outside the team
- Cross-functional:teams have all competencies needed to accomplish the work withoutdepending on others not part of the team

1 - The Product Owner
> The Product Owner is responsible for maximizing the value of the product and the work of the Development Team
> The Product Owner is the sole person responsible for managing the Product Backlog.
> Product Backlog management includes:
a) Clearly expressing Product Backlog items;
b) Ordering the items in the ProductBacklog to best achieve goals and missions;
c) Ensuring the value of the work the Development Team performs;
d) Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,
e) Ensuring the Development Team understands items in the Product Backlog to the level needed.
> For the Product Owner to succeed, the entireorganization must respect his or her decisions
> No one is allowed to tell the Development Team to work from a different set of requirements, and the Development Team isn’t allowed to act on what anyone else says.

2 - The Development Team
> The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of eachSprint.
> Development Teams have the following characteristics:
a) They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality;
b) Development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment;
c) Scrum recognizes no titlesfor Development Team members other than Developer, regardless of the work being performed by the person; there are no exceptions to this rule;
d) Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole; and,
e) Development Teams do not contain sub-teams dedicated to particular domains like testing or...
tracking img