Daniel bill-scrum


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

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

No notes for slide
  • Characteristic of the translationFix time, Sep -> Feb. 13Fix scope, 21 chapter+2 appendixesFix resources, Gang of FourWe like this classic book and believe agile community in China wants it, decide to contribute as volunteers
  • AssumptionsEvery body have access to latest versionThings will go smoothly, Every one will volunteer to sign up what to doWe are good at English and Chinese, good passion for Agile, Enough timeEmail (or Phone call) should me enoughRealitySomebody puts into google doc, somebody puts into subversion, emailActual velocity - One chapter per monthWhat you guys are doing?Less than 10 mails , No phone call
  • Show the spread sheetThe point on Nov 15Central Kanban file to help communicate&coordinate the tasks and what to doAvoid conflictingChapter as unit of workMake sure kanban file reflect the latest statusDone Definition
  • TimeboxWeekly sync meeting on Skypethree questionsIssues & ImpedimentAgreement on common terms such Epic, Theme, StoryHard sentences brainstorm, external dependency of MikeretrospectivePeer PressureLearn from fast feedbackChapter pointWhy only a rough estimate? Each chapter relative within the same rangeJust enough estimateDone DefinitionCheck pointPlanned velocity(1.5 chapter per week)More Commitment
  • In addition to email and weekly meetingWe use Continuous Integration check in comment to communicate, Important part of communicationUpdate burndown when commiting
  • 281 check-ins in total
  • Time to ChangeTrend visualized
  • Chapter Done over Task DoneFinished review, not acceptedBig dropBenefitSmall batch sizeTest early to get more knowledge as early as possibleWe are late – How to meet the deadline?
  • Bill and Daniel started to contributeAgree on 2 reviewer including J & SRole blurred, Real cross-functional team, real collaboration
  • Discovered more workAdded two Chapter pointsInitial releaseWe are late, we want to push to market before Scrum GatheringRelease 10 Chapters firstRelease review of the first 10 Chapters
  • New work: 2 pointsAll partsRelease 10 chapters, Because it is done, we can release anytimeDone Definition: Fix issues( new knowledge), make it better
  • One week late
  • KanbanTask coordinationMeetingWhere we are?Peer PressureLearning pointIssue resolved ASAPFail fast with less costEnable self-organizationProcess issueTask assignment and coordinationHelp each otherChange directionTeam strategy changeCross-functional – two reviewersChange done definitionCI HistoryCommunication and feedback tool - instantEmails as backup
  • Small batch End-to end chaptersBetter measurement of progress leads to more predictability and visibilityMore coordination pointless waiting, less bottleneck leads to faster flowFail fast, lower cost to fix problems, prevent future failuresCan release to publish house anytimeChapter pointJust enough planningCommitmentPeer presureFrequent check pointTimebox as learning point and sync pointBurndown to indicate the ideal vs realityFeel the pressureOnly measure DONE workVisualize the workKanban to visualize all the work to be doneResponsibility is clear
  • Review as early as possibleThe earlier to test, the shorter the feedback loop, the more we learnChapter doneOnly measure done work enforced WIPPrefer done story to sign up new taskEveryone sign up any taskNo bottleneckNo local optimization
  • PO is very happy about the resultPO is not used to new strategyIf every chapter done, then can release to PO to get early feedbackTerms check, common issues check to CI
  • Behavior change technique Kanban, Burndown, Regular check points More self-organizingCommunicationMeans - Weekly meeting, Continuous Integration, EmailsPush modelSpread knowledgeFeedback is goodTest early to get more knowledge, to learnTo communicate knowledge with whole teamSelf-organization is good Common visionLess role distinctionAvoid local optimizationOptimize the queueMore creative on processMore ownership
  • Daniel bill-scrum

    1. 1. AGILE Beyond Software<br />
    2. 2. What We Did<br />2<br />
    3. 3. Who Are We?<br />Reviewer<br />Daniel Teng, CSM, CSP<br />InfoQ Editor<br />Reviewer<br />Bill Li, Agile Evangelist<br />CSM, CSPO, CSP<br />Translator<br />Jackson Zhang, CSM, CSP<br />Translator<br />Stone Shi, CSM<br />InfoQ Editor<br />
    4. 4. Dark age<br />4<br />Assumptions vs. Reality<br />
    5. 5. Time to change – Nov. 15th<br />Communication<br />Visibility<br />Planning and Tracking<br />Collaboration & Synchronization<br />Quality<br />5<br />
    6. 6. Kanban<br />6<br />Worker<br />Procedures,<br />Done Definition<br />Work<br />
    7. 7. Burndown<br />7<br />Check Point<br />Unit of Measure<br />Timebox<br />
    8. 8. Continuous Integration<br />8<br />Send to everyone<br />Message<br />Change that made<br />
    9. 9. Continuous Integration<br />9<br />281 in total<br />
    10. 10. Big Turning Point<br />10<br />Already far behind<br />
    11. 11. 11<br />Why this happened?<br />
    12. 12. 12<br />Too much work undone<br />
    13. 13. 13<br />We are still late<br />
    14. 14. 14<br />Bill/Daniel started developing<br />
    15. 15. 15<br />Discovered more Work<br />
    16. 16. 16<br />New Done Definition<br />Release 10 chapter first<br />New Work<br />
    17. 17. 17<br />One week late<br />More work done<br />
    18. 18. How Do We Solve Communication Problem<br />Kanban<br />Weekly Sync Meeting<br />Status<br />Commitment<br />Impediment<br />Retrospective<br />Continuous Integration<br />Emails <br />18<br />
    19. 19. How Do We Plan And Track<br />Small batch size<br />Chapter point<br />Commitment based<br />Frequent check point<br />Visualize the work<br />19<br />
    20. 20. Rules For Signing Up Tasks<br />Review as early as possible<br />Prefer chapter done to signing up new task<br />Everyone sign up any task<br />Make sure Kanban update to date<br />20<br />
    21. 21. Queue Theory<br />Little’s Law for Queuing Theory<br />21<br />Total Cycle Time = Number of Things in Process<br />Average Completion Rate<br />
    22. 22. Strategy for Queue<br />Limit number of things in process<br />Increase average completion rate<br />Make task smaller<br />Reduce variability<br />Arrival<br />Process<br />More servers for one task queue<br />22<br />
    23. 23. Small is good<br />23<br />
    24. 24. Tools We Used<br />Spread sheet<br />Kanban<br />Burndown<br />Subversion<br />CruiseControl.Net<br />Skype<br />Email<br />24<br />
    25. 25. Can We Do Better?<br />Educate the Product Owner/More PO involvement<br />Release by chapter<br />Include automated check to CI<br />…<br />25<br />
    26. 26. What We Learned<br />Agile is not only for software<br />Many agile practices change human behaviors<br />Agile tools help solve people problems<br />Key factors of project success<br />Ensure communication<br />Feedback is good<br />Self-organization works well<br />Prefer simple tools<br />Inspect and adapt <br />26<br />
    27. 27. Question?<br />Bill: bill.li@ScrumChina.comDaniel: tengzhenyu@gmail.com<br />Jackson: zbcjackson@gmail.com Stone: choushi@gmail.com<br />27<br />
    28. 28. 28<br />Thanks<br />