Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Why Do We Scrum? - ProductCamp Toronto-2016

363 views

Published on

When it comes to project management, people often don't understand why scrum process is needed. You may have Jira with a bunch of tasks and stand-up meetings, but it won't give you any understanding of how good is project going. Ultimately at each moment of time you want to be sure that everything will be delivered on time, and if not, discover issues sooner than later. So now you need to understand, and make other people on your team understand why is it all needed.
- How scrum can be used in non-agile environment?
- Why tasks are planned ahead once in the beginning of the sprint instead of giving tasks to people every day?
- Why and how stories should be divided into sub-tasks?
- How to understand, if your developers are doing good job, if you are a non-technical person?

Published in: Software
  • Be the first to comment

  • Be the first to like this

Why Do We Scrum? - ProductCamp Toronto-2016

  1. 1. TED ROGERS SCHOOL OF MANAGEMENT, RYERSON UNIVERSITY ProductCamp July 23th 2016 www.productcamptoronto.wordpress.com WHY DO WE SCRUM? ROMAN TEMCHENKO SOFTWARE DEVELOPER
  2. 2.  Get customer feedback early  Track project health To deliver better product in time Why do we scrum?
  3. 3. Always  Inspect and Adapt  Product Increment  Definition of Done Every project uses these principles. Scrum is only a framework to make it easier. When is scrum applicable?
  4. 4.  Provide the big picture of planned work  Explain the desired result  Explain the purpose  Make team feel the timeline It is easier to play tetris when you get 5 pieces at a time. Not 1 and not 100. Sprint planning
  5. 5. User Stories  Independent, Negotiable, Valuable, Estimable, Small, Testable – a bit hard, but OK Sub Tasks  1-2 days each, if more break it down  Chain of sub tasks  All parts of product under one story  You can always adjust and break it down User stories and sub-tasks
  6. 6.  The key to health monitoring  What did you do yesterday? - If you broke yesterday commitment, explain why.  What will you do today? - It is a commitment. If you break it, you will have to explain tomorrow what happened.  Are there any impediments in your way? - You don’t have to wait for next scrum to tell your manager or any other interested parties about it. Daily stand-up
  7. 7.  Broken commitments are the main issue  And there will be tons of them  Many small broken commitments can pile up and lead to a bigger failure  So don’t let those pile up and address right away Project health
  8. 8.  A small milestone  Get client feedback Demo part
  9. 9.  Sum up health of the project  Sum up debt  Discuss steps to improve Retrospective
  10. 10. Roman Temchenko Software Developer temchenko.r@gmail.com Thank you!

×