8
Scrum Implementation SilverSearch

Scrum implementation

Embed Size (px)

Citation preview

Page 1: Scrum implementation

Scrum ImplementationSilverSearch

Page 2: Scrum implementation

Why do we choose Scrum for our Project? Managing Scope Stability:( clarifying requirements or reducing the project scope before starting Sprint Iteration) Scrum time-boxed challenges: (Sprint duration, velocity, burn-down/ up charts) Increase short-term predictability and transparency Richer communication techniques:(Scrum ceremonies, team self-estimation)

Page 3: Scrum implementation
Page 4: Scrum implementation
Page 5: Scrum implementation
Page 6: Scrum implementation

Statements to follow:• No stories tasks without estimation in an active Sprint backlog.• All stories should include the estimated time for testing;• Unit test and refactoring tasks should be followed;• No product backlog increment within a Sprint. • Set a multi-tasking limit per user. Suggestion: no more than 2 tasks “in

progress” for 1 developer. • Create and follow Definition of Done.

Page 7: Scrum implementation

Definition of Done (DoD): • Is a checklist of valuable activities required to produce software The team

defines definition of done for each iteration, feature, requirement task, etc.• Typically • Software working? • Unit tests written?• Code review done? • Functional tests written and passed? • Non-functional tests written and passed?• User documentation done and reviewed? • Design documentation updated and reviewed?

Page 8: Scrum implementation