1 / 28

AGILE Beyond Software

AGILE Beyond Software. What We Did. Who Are We?. Reviewer Daniel Teng, CSM, CSP InfoQ Editor. Reviewer Bill Li, Agile Evangelist CSM, CSPO, CSP. Translator Jackson Zhang, CSM, CSP. Translator Stone Shi, CSM InfoQ Editor. Assumptions vs. Reality. Dark age. Communication

lynna
Download Presentation

AGILE Beyond Software

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AGILE Beyond Software

  2. What We Did

  3. Who Are We? Reviewer Daniel Teng, CSM, CSP InfoQ Editor Reviewer Bill Li, Agile Evangelist CSM, CSPO, CSP Translator Jackson Zhang, CSM, CSP Translator Stone Shi, CSM InfoQ Editor

  4. Assumptions vs. Reality Dark age

  5. Communication Visibility Planning and Tracking Collaboration & Synchronization Quality Time to change – Nov. 15th

  6. Kanban Worker Procedures, Done Definition Work

  7. Burndown Check Point Unit of Measure Timebox

  8. Continuous Integration Send to everyone Message Change that made

  9. Continuous Integration 281 in total

  10. Big Turning Point Already far behind

  11. Why this happened?

  12. Too much work undone

  13. We are still late

  14. Bill/Daniel started developing

  15. Discovered more Work

  16. New Done Definition Release 10 chapter first New Work

  17. One week late More work done

  18. Kanban • Weekly Sync Meeting • Status • Commitment • Impediment • Retrospective • Continuous Integration • Emails How Do We Solve Communication Problem

  19. Small batch size Chapter point Commitment based Frequent check point Visualize the work How Do We Plan And Track

  20. Review as early as possible Prefer chapter done to signing up new task Everyone sign up any task Make sure Kanban update to date Rules For Signing Up Tasks

  21. Total Cycle Time = Number of Things in Process Average Completion Rate Little’s Law for Queuing Theory Queue Theory

  22. Limit number of things in process • Increase average completion rate • Make task smaller • Reduce variability • Arrival • Process • More servers for one task queue Strategy for Queue

  23. Small is good

  24. Spread sheet • Kanban • Burndown • Subversion • CruiseControl.Net • Skype • Email Tools We Used

  25. Educate the Product Owner/More PO involvement Release by chapter Include automated check to CI … Can We Do Better?

  26. Agile is not only for software • Many agile practices change human behaviors • Agile tools help solve people problems • Key factors of project success • Ensure communication • Feedback is good • Self-organization works well • Prefer simple tools • Inspect and adapt What We Learned

  27. Bill: bill.li@ScrumChina.comDaniel: tengzhenyu@gmail.com Jackson: zbcjackson@gmail.com Stone: choushi@gmail.com Question?

  28. Thanks

More Related