Like many conveniences in software development, a shared database is a tar pit waiting to fossilize a project. Developers overwrite each other’s changes. The changes I make on the server break the code on your development machine. Remote development is slow and difficult. Avoid using a shared database at all costs, as they ultimately waste time and help produce bugs.
Scrum Development Model
Download pdf : http://docs.issani.in/dump/scrum-tuts-100219-v2.1.pdf
Scrum DevelopmentModel email@example.com Required Steps1) Get your backlog in order 1. Involve stakeholders 2. Create list of product actions 3. Prioritize this list 4. Get list confirmed with product owner 5. Discuss list with team2) As a team, estimate your Product backlog 1. Provide a high-level guess/estimate 2. Product owner reviews priorities3) As a team, plan Sprint requirements 1. Call a sprint planning meeting 2. Ensure that whole team attends 3. Decide sprint duration (weekly/monthly) 4. Select target backlog items for sprint 1. Choose high priority items first 5. Clarify sprint requirements 1. Methodically go through each item at a time 2. Ask product owner to present each item from functional perspective 3. Discuss the items in detail 5. Write requirements by feature4) As a team, plan Sprint tasks 1. Break requirements into tasks 1. Go through each backlog item 2. Break these tasks down further 3. Include all items to make the Product backlog item 100% complete 2. Estimate tasks in hours 3. Commit to the Sprint backlog 1. remove lower items (according) if exceeding sprint capacity 4. Identify stretch/delayable tasks5) Create an effective collaborative workspace 1. use some software tool or the traditional whiteboard Required Steps (contd.)6) ‘Sprint’ to achieve the Sprint goal 1. Understand that the sprint duration is fixed 2. If you finish early, include more scope 3. If you’re behind reduce scope 4. Ensure that you complete one feature at a time to 100% (that includestesting)7) Optimize Stand up meetings (Scrums) 1. Scrum master should ensure that impedances are removed 2. Keep meetings to 15 minutes maximum 3. Ensure everyone answers 3 questions 1. what u did since last scrum 2. what you’re planning to finish by next scrum 3. Any blocks or impediments that are in their way 4. Note that the Daily Scrum is not a status meeting to report to a manager8) Track progress with a Daily burndown chart 1. Update estimated time to complete (ETC) daily 2. Ensure individuals update their own ETC before daily scrum 3. Plot progress visually on graph (burndown chart)9) Finish on schedule10) Review 1. At the end of the sprint, hold a sprint review meeting 2. Team members demo the software 3. Review the burndown chart 4. Discuss what went well 5. Discuss what could be improved and improvements for the next sprint