• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Scrum소개
 

Scrum소개

on

  • 3,474 views

LG 전자, 엄위상

LG 전자, 엄위상

Statistics

Views

Total Views
3,474
Views on SlideShare
1,636
Embed Views
1,838

Actions

Likes
3
Downloads
0
Comments
0

3 Embeds 1,838

http://agilekorea.org 1423
http://k16wire2.cafe24.com 411
http://translate.googleusercontent.com 4

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 실패의 원인은 ? Tool? 영어 능력 ? 잘못된 개발 전략 (Waterfall)

Scrum소개 Scrum소개 Presentation Transcript

  • 엄 위 상 @wseom Introduction to Scrum [email_address]
  • Who am I?
    • 현재 LG 전자 SW 역량강화센터 재직 중
      • Agile coach & Trainer
      • 주요 Activity: TDD, ATDD, Refactoring, Scrum, Pair programming
    • 취미
      • 번역 : Software 관련 서적 번역
      • 통역 : 사내외 SW 관련 교육과정 / 세미나
  • World No.1 Korea Source: Organization for Economic Cooperation and Development
  • 개발자의 현실
  •  
  •  
  • 어느 독자의 서평 결론 : 프로젝트 관리자라면 이 책을 반드시 읽어보기 바란다 . 자 ... 독자 여러분께서 학수고대하던 까칠 모드로 들어간다 . 이 책을 읽다보니 역자들이 서두르는 바람에 , 충분히 뜸이 들지 않았다는 생각이 떠나지 않았다 . 즉 , 완성이 덜 된 느낌이 든다 . …
  • 왜 그랬을까 ?
    • Tool?
      • Google Office
      • 맞춤법 검사기
      • On-Line Dictionary
    • Personal Ability?
    • Strategy!
      • Waterfall Style Development : Job Assign/ Divide & Merge
      • No knowledge for other’s chapters
      • No deliverable until almost the end
      • No Transparency
  • 재 도전
  •  
  • 다시 서평 읽어보니 훌륭한 책이네요 .   일단 책이 너무 쉽게 잘 읽힙니다 . 아무리 좋은 내용이 담겨있더라도 잘 읽혀지지 않는 책들은 가치가 떨어지게 마련이지요 . 최근에 읽은 책중에 번역이 최고라고 할 수 있습니다 . 읽다가 번역때문에 갸우뚱하는 경우가 거의 없습니다 . …
  • Scrum Implementation
  • What is SCRUM?
    • Scrum is
    • : A simple framework for project management on complex project.
      • Empirical management & control process
      • – inspect and adapt feedback loops;
      • • Used to manage complex projects since 1990;
      • • Delivers business functionality in 30 days;
      • • Scalable to distributed, large, and long projects;
      • • Extremely simple but very hard.
  • SCRUM Cycle
  • Quiz
    • Scrum 의 3 명의 등장 인물 ?
    • Scrum 의 3 가지 산출물 ?
    • Scrum 의 3 가지 Activity?
  • Scrum process Week 1 Week 2 Week 3 Timeline Sprint 1 Sprint-planning Sprint Demo Sprint-planning Estimated velocity = X Actual velocity = Y Goal: xyz Daily Scrum Daily Scrum release Sprint 2 Produkt Backlog Sprint 1 Backlog
  • Team
    • 3 – 8 full-time individuals
    • Cross-functional
    • Sits together
    • Shared responsibility
    • Self-organizing
    • 3 roles
    • Product owner
    • Scrum master
    • Team
    • 3 artifacts
    • Product backlog
    • Sprint backlog
    • Sprint burndown
    • 3 activities
    • Sprint planning
    • Daily scrum
    • Sprint review
      • Demo
      • Retrospective
    SM
  • Product owner
    • Represents all stakeholders
    • Decides where the team should go
      • Not how they get there
      • Not their speed
    • Defines scope / vision / roadmap
    • Prioritizes
    • Owns product backlog
    • Does not estimate stories
    • Usually Not the line manager
    • 3 roles
    • Product owner
    • Scrum master
    • Team
    • 3 artifacts
    • Product backlog
    • Sprint backlog
    • Sprint burndown
    • 3 activities
    • Sprint planning
    • Daily scrum
    • Sprint review
      • Demo
      • Retrospective
    PO
  • ScrumMaster
    • Enforces Scrum practices
      • Coaching rather than command & control
    • Removes obstacles
    • Usually part of the team
    • Usually Not the line manager
    • Usually Not the tech guru
    • 3 roles
    • Product owner
    • Scrum master
    • Team
    • 3 artifacts
    • Product backlog
    • Sprint backlog
    • Sprint burndown
    • 3 activities
    • Sprint planning
    • Daily scrum
    • Sprint review
      • Demo
      • Retrospective
    Is ScrumMaster a full-time role?
    • 장애 목록
    • Slow workstations
    • Interference from sales
    • No test environment
    • No contact with customer
    • Crowded office
    SM Small team Large team Few problems ≈ 10% ≈ 50% Many problems ≈ 50% 100%
  • Product backlog Product Backlog
    • 3 roles
    • Product owner
    • Scrum master
    • Team
    • 3 artifacts
    • Product backlog
    • Sprint backlog
    • Sprint burndown
    • 3 activities
    • Sprint planning
    • Daily scrum
    • Sprint review
      • Demo
      • Retrospective
    ID Name Imp Est How to demo Notes 1 Deposit 30 5 Log in, open deposit page, deposit €10, go to my balance page and check that it has increased by €10. Need a UML sequence diagram. No need to worry about encryption for now. 2 See your own transaction history 10 8 Log in, click on “transactions”. Do a deposit. Go back to transactions, check that the new deposit shows up. Use paging to avoid large DB queries. Design similar to view users page.
  • Story I ndependent N egotiable V aluable E stimable S mall T estable As a < role > I want to < what > so that < why >
    • 3 roles
    • Product owner
    • Scrum master
    • Team
    • 3 artifacts
    • Product backlog
    • Sprint backlog
    • Sprint burndown
    • 3 activities
    • Sprint planning
    • Daily scrum
    • Sprint review
      • Demo
      • Retrospective
    • How to demo:
    • Enter store
    • Put a book in shopping cart
    • Press ”save cart”
    • Leave store, and enter it again
    • Check that the book is in my cart
    As a buyer I want to save my shopping cart so that I can continue shopping later 8
  • Definition of Done
    • Default Definition of Done
    • Acceptance tested
    • Release notes written
    • Releasable
    • No increased technical debt
    • Default Definition of Done
    • Unit/Integration tested
    • Ready for acceptance test
    • deployed on demo server
    = I haven’t messed up the codebase
    • Default Definition of Done
    • Releasable
    What’s NOT included in DoD? - For example ”customer acceptance test + user documentation” Why not? Who does it? When? What happens if a problem turns up?
  • Sprint planning meeting - example
    • Goal
    • Present backlog
    • Reprioritize, Re-estimate, split stories, combine stories
    • Break out tasks
    • Estimate velocity, draw the line
    More important Less important 8 13 3 13 8 5 5 2h 12h 8h 4h 8h GOAL: Beta-ready release!
    • 3 roles
    • Product owner
    • Scrum master
    • Team
    • 3 artifacts
    • Product backlog
    • Sprint backlog
    • Sprint burndown
    • 3 activities
    • Sprint planning
    • Daily scrum
    • Sprint review
      • Demo
      • Retrospective
    20 Encrypted Password Deposit Migration tool Backoffice login Backoffice User admin Withdraw Perf Test User Migration tool Transaction Migration tool DB design Impl. DAO Integr Test Refact. Write failing test
  • Sprint backlog – day 0
    • 3 roles
    • Product owner
    • Scrum master
    • Team
    • 3 artifacts
    • Product backlog
    • Sprint backlog
    • Sprint burndown
    • 3 activities
    • Sprint planning
    • Daily scrum
    • Sprint review
      • Demo
      • Retrospective
  • Daily Scrum meeting
    • 15 minutes
    • 지난 하루 동안 어떤 일을 했나 ?
    • 다음 하루 동안 어떤 일을 할 것인가 ?
    • 어려운 점이 무엇인가 ?
    • 3 roles
    • Product owner
    • Scrum master
    • Team
    • 3 artifacts
    • Product backlog
    • Sprint backlog
    • Sprint burndown
    • 3 activities
    • Sprint planning
    • Daily scrum
    • Sprint review
      • Demo
      • Retrospective
  • Sprint backlog – after 1st meeting
    • 3 roles
    • Product owner
    • Scrum master
    • Team
    • 3 artifacts
    • Product backlog
    • Sprint backlog
    • Sprint burndown
    • 3 activities
    • Sprint planning
    • Daily scrum
    • Sprint review
      • Demo
      • Retrospective
  • Sprint burndown chart
    • 3 roles
    • Product owner
    • Scrum master
    • Team
    • 3 artifacts
    • Product backlog
    • Sprint backlog
    • Sprint burndown
    • 3 activities
    • Sprint planning
    • Daily scrum
    • Sprint review
      • Demo
      • Retrospective
  • Sprint backlog – day X
    • 3 roles
    • Product owner
    • Scrum master
    • Team
    • 3 artifacts
    • Product backlog
    • Sprint backlog
    • Sprint burndown
    • 3 activities
    • Sprint planning
    • Daily scrum
    • Sprint review
      • Demo
      • Retrospective
  • Sprint demo
    • Team demonstrates working code to stakeholders
    • Only 100% completed stories are demonstrated
      • Partially completed stories ignored
    • Direct feedback from stakeholders
    • Feedback incorporated into product backlog
    What have we accomplished?
    • 3 roles
    • Product owner
    • Scrum master
    • Team
    • 3 artifacts
    • Product backlog
    • Sprint backlog
    • Sprint burndown
    • 3 activities
    • Sprint planning
    • Daily scrum
    • Sprint review
      • Demo
      • Retrospective
  • Team Member 의 할 일 Sprint Meeting 전에… * 내가 이번 스프린트에 며칠이나 쉴지 파악해 놓는다 . Sprint Meeting 중에… * 스프린트 목표를 달성하려면 어떤 작업들을 해야 하는지 , 작업량은 얼마나 될지 고민한다 . Daily Scrum Meeting 전에… * 내가 시작한 작업에 대해 남은 작업량을 업데이트한다 . Daily Scrum Meeting 중에… * 어제 한 일 , 오늘 할 일 , 애로사항을 이야기한다 . Sprint 중에 * 할 일을 열심히 한다 . * 작업이 진행되면서 현황판의 작업 목록을 적절히 옮긴다 .
  • Product Owner 의 할 일 Sprint Meeting 전에… * Product Backlog 의 우선 순위를 재정비한다 . Sprint Meeting 중에… * Product Backlog 를 설명한다 . Daily Scrum Meeting 중에… * 궁금하면 참석하여 상황을 파악한다 . ( 끼어들고 싶어도 참는다 ) Sprint 중에 * 팀이 개발 잘하도록 서포트한다 . ( 우선순위를 바꾸고 싶어도 다음 스프린트까지 참는다 )
  • Scrum Master 의 할 일 Sprint Meeting 전에… * Product Owner 와 함께 Product Backlog 를 리뷰한다 . Sprint Meeting 중에… * Meeting 이 잘 진행되도록 도와준다 . Daily Scrum Meeting 중에… * Team Member 들이 이야기하는 장애요소를 메모한다 . * 언급되지 않은 숨은 문제를 파악하고자 노력한다 . Sprint 중에 * 장애요소를 Product Owner 와 함께 해결하기 위해 동분서주 ..
  • Product Backlog Sprint Backlog 우선순위 ( 중요도 ) 작업량 추정치 (Ideal Man-day) 데모방법 작업량 추정치 (Ideal Man-hour) Estimate Velocity Available Man-day * 50% 기타 Daily Scrum 은 언제 , 어디서 Demo 날짜 장소 Definition of Done Sprint Goal 이번 스프린트에 이것만은 ! 첫 번째 스프린트를 위해 준비할 것들 팀원 일하는 날 아무개 홍길동 춘향이 15 13 13 Available 41
  • What makes it hard?
  • Legacy Code!
  • It makes everything hard!
      • Estimation
      • Deliver within sprints
      • Continuous Integration
      • TDD & Refactoring
  • What makes it hard?
  • ScrumBut
    • We do Scrum but …
      • don’t do daily scrum. We do it per week
      • don’t do retrospective since it is waste of time
      • our sprint is 2 months long.
      • don’t have the DoD.
  • It seems to work, but …
  • What actually happens is …
  • Announcement 2012.2.7 ~ 2.8
  • Summary
    • Agile Development is Essential for current Projects
      • Gartner Group : “By 2012, agile development methods will be utilized in 80% of all software development projects”
    • Avoid ScrumBut
    • - Follow the rule strictly!
    • Technical Agility
      • Agility strongly depends on technical agility
        • Continuous Integration
        • Development Practices: Refactoring, TDD, Pair Programming, … in the right way
    @wseom