BamBam! Teamwork Academy: Scrum


Published on

BamBam! Teamwork Academy is a new series by 84kids focusing on online collaboration, project management and Agile approach to software development.

Each presentation contains a number of useful tips that can be applied in practice to all kinds of development business, from small software houses to engineering companies running on workflows to large production ventures.

Feel free to comment and share!

Published in: Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

BamBam! Teamwork Academy: Scrum

  1. 1. # Scrum
  2. 2.  Scrum is an Agile software development framework based on increment and iteration  The key principle of Scrum is recognition that customers can change their mind about what they need during the process of building software  Scrum focuses on adoption and quick response to changes  The word Scrum comes from rugby football lingo and refers to the manner of restarting the game after a minor infraction What is Scrum? # Scrum
  3. 3.  What is more important for you: individuals and interactions or processes and tools?  Do you spend more time making your product usable or making documentation how to use it?  Would you rather collaborate with your clients or negotiate hard?  Are you able to respond to changes on-the-fly or do you stick to the plan no matter what? # Scrum Will Scrum work for my company?
  4. 4. If you chose at least one answer in bold then Scrum is definitely worth giving a shot # Scrum
  5. 5. Three core roles in Scrum  Scrum Master – ensures that Scrum proceeds with no impediments and the team achieves product goals and deliverables  Product Owner – represents the client and builds the roadmap for the product in form of a prioritised backlog  Development Team – responsible for delivering the actual product in form of potentially shippable increments. Scrum teams are usually small (up to 10 people) with members of cross-functional skills # Scrum
  6. 6. Scrum sprint chart # Scrum
  7. 7.  Daily Scrum – a timeboxed meeting where all members of the development team report on the progress of their work and indicate impediments  Sprint retrospective meeting – at the end of each cycle the team gathers to reflect what went well in the sprint and what can be improved  Sprint review meeting – stakeholders are presented completed work in form of a demo. Incomplete work and possible changes are discussed Events in Scrum # Scrum
  8. 8. Scrum burndown chart # Scrum
  9. 9.  Poor or lack of communication  No retrospective meetings  Badly constructed teams (no complementation)  No customer participation  Poor planning # Scrum Common mistakes of new Scrum teams
  10. 10.  Use abstract estimation points (like colors or shapes) to represent the size of new work  Don’t use deadlines until you and your team know how quickly a task can be completed  Engage your team in planning iterations and respect the value of their insights  Give your team a prioritized list of requests (backlog) rather than a set of directives  Always foster an environment of trust in your company # Scrum How to make your team commissioned
  11. 11. Yes, let’s do this! Ready to apply Scrum in practice?