SilverSearch is implementing Scrum for their project to manage scope stability, leverage Scrum time-boxing techniques, and increase short-term predictability and transparency through richer communication. Key aspects of the Scrum implementation include not having stories or tasks without estimates in the Sprint backlog, including testing estimates in all stories, following unit test and refactoring tasks, not having product backlog increments within a Sprint, limiting developers to no more than 2 in-progress tasks, and creating and following a Definition of Done checklist.

1. Scrum Implementation
SilverSearch

2. 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)

6. 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.

7. 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?