Scrum

759 views

Published on

Published in: Technology
  • Be the first to comment

Scrum

  1. 1. Principles
  2. 2. Principle 시공을 초월하여 변하지 않는 근원적인 진실 Practice 원칙을 특정 상황에 맞게 적용한 것 .
  3. 3. learn by doing + understand-before-doing
  4. 5. What is SCRUM ?
  5. 6. 경직되어 있고 변화에 저항하는 프로세스는 그저 그런 제품을 만들어 낸다 .
  6. 7. a process with a set of roles and practices for agile development and project
  7. 8. iterative = timeboxed (sprints)
  8. 9. incremental = features added incrementally
  9. 10. continuous process improvements = retrospectives
  10. 11. continuous process improvements = retrospectives
  11. 12. 최종 사용자 , 고객 , 팀 및 기타 이해당사자들로부터의 입력 제품 책임자 기능들 제품 백로그 스프린트 종료까지 얼마나 많이 해낼 것 인지 약속할 항목 들을 팀이 선택 스프린트 계획회의 (1 부와 2 부 ) 스프린트 백로그 기간 내에 혹은 목표에 변화 없음 스프린트 (1~4 주 ) 제품 백로그 구체화 스크럼 마스터 일일 스크럼 회의와 산출물 갱신 리뷰 잠재적으로 출시 가능한 제품 증분 회고
  12. 13. Backlog
  13. 14. Roles – Pigs and Chickens #1 <ul><li>A pig and a chicken are walking down a road. The chicken looks at the pig and says, &quot;Hey, why don't we open a restaurant?&quot; The pig looks back at the chicken and says, &quot;Good idea, what do you want to call it?&quot; The chicken thinks about it and says, &quot;Why don't we call it 'Ham and Eggs'?&quot; &quot;I don't think so,&quot; says the pig, &quot; I'd be committed but you'd only be involved .“ </li></ul><ul><li>Ham and Eggs - committed or </li></ul><ul><li>just involved </li></ul>
  14. 15. Roles – Pigs and Chickens #2 <ul><li>Pigs </li></ul><ul><ul><li>Product Owner - voice of the customer </li></ul></ul><ul><ul><li>Scrum Master - enforcer of Scrum process, facilitates (removing impediments) team to reach sprint goal </li></ul></ul><ul><ul><li>Team - cross-functional (design, developer, test), usually 5-9 people who does the work </li></ul></ul><ul><li>Chickens </li></ul><ul><ul><li>Users </li></ul></ul><ul><ul><li>Stakeholders (Customers, Vendors) </li></ul></ul><ul><ul><li>Managers </li></ul></ul>
  15. 16. Sprint Timeboxed iteration Usually 2-4 weeks Determine sprint goal Working functionality
  16. 17. Sprint Planning Meeting <ul><ul><li>Timeboxed at 4 hours </li></ul></ul><ul><ul><li>Team to negotiate with product owner what to put in sprint </li></ul></ul><ul><ul><li>Determine the sprint goal (specific, measurable, demonstratable) </li></ul></ul><ul><ul><li>Translate user stories into &quot;how&quot; a requirement is to be built </li></ul></ul>
  17. 18. Whiteboard and Post-It’s
  18. 19. Whiteboard and Post-It’s
  19. 20. Daily Scrum 지난 일일 스크럼 이후 무엇을 완료하였는가 ? 다음 회의 때까지 무엇을 마무리할 계획인가 ? 일하는 데 어떠한 방해나 장애요인들이 있는가 ? Daily 15 minute
  20. 21. Burn Down Charts
  21. 22. SCRUM Process <ul><li>create product backlog </li></ul><ul><ul><li>(product owner, customer => prioritized user stories) </li></ul></ul><ul><li>create sprint backlog - sprint planning meetings </li></ul><ul><ul><li>(involves product owner, scrum master, team) </li></ul></ul><ul><li>execute sprint </li></ul><ul><ul><li>daily scrum meetings </li></ul></ul><ul><ul><li>Scrum Master to remove impediments </li></ul></ul><ul><ul><li>progress tracked with whiteboard, burn-down charts </li></ul></ul><ul><li>sprint review </li></ul><ul><ul><li>demo, invite everyone including customer </li></ul></ul><ul><ul><li>was the sprint goal met according to customer? </li></ul></ul><ul><li>sprint retrospective (continuous improvements) </li></ul><ul><ul><ul><li>what do we want to start doing? </li></ul></ul></ul><ul><ul><ul><li>what do we want to stop doing? </li></ul></ul></ul><ul><ul><ul><li>what do we want to keep doing? </li></ul></ul></ul>
  22. 23. mechanism 단지 구체적인 실천법을 모아둔 것이라기보다는 팀에게 가시성을 제공하는 프레임워크이며 가시성을 바탕으로 팀이‘관찰하고 적응하게’한다 .
  23. 24. Reference Book “Agile Software Development with SCRUM” by Ken Schwaber, Mike Beedle Book “Agile Project Management with SCRUM” by Ken Schwaber http :// www.scrumalliance.org / http:// www.controlchaos.com / - Ken Schwaber’s own site

×