Agile Beyond Software

Post on 22-Jun-2015

2.524 views 0 download

Tags:

description

This is experience sharing about how we applied agile techniques into our book translation project. How do you inspect and adapt.

Transcript of Agile Beyond Software

AGILE BEYOND SOFTWARE

WHAT WE DID

2

WHO ARE WE?

ReviewerDaniel Teng, CSM, CSP

InfoQ Editor

ReviewerBill Li, Agile EvangelistCSM, CSPO, CSP

TranslatorStone Shi, CSMInfoQ Editor

TranslatorJackson Zhang, CSM, CSP

DARK AGE

4

Assumptions vs. Reality

TIME TO CHANGE – NOV. 15TH

Communication Visibility Planning and Tracking Collaboration & Synchronization Quality

5

KANBAN

6

Work

Procedures,Done Definition

Worker

BURNDOWN

7

Check Point

Timebox

Unit of Measure

CONTINUOUS INTEGRATION

8

Send to everyone

Message

Change that made

CONTINUOUS INTEGRATION

9

281 in total

BIG TURNING POINT

10

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 Work

New Done Definition

Release 10 chapter first

17

One week lateMore work done

HOW DO WE SOLVE COMMUNICATION PROBLEM

Kanban Weekly Sync Meeting

Status Commitment Impediment Retrospective

Continuous Integration Emails

18

HOW DO WE PLAN AND TRACK

Small batch size Chapter point Commitment based Frequent check point Visualize the work

19

RULES FOR SIGNING UP TASKS

Review as early as possible Prefer chapter done to signing up new

task Everyone sign up any task Make sure Kanban update to date

20

QUEUE THEORY

Little’s Law for Queuing Theory

21

Total Cycle Time = Number of Things in Process Average Completion Rate

STRATEGY FOR QUEUE

Limit number of things in process Increase average completion rate Make task smaller Reduce variability

Arrival Process

More servers for one task queue

22

SMALL IS GOOD

23

TOOLS WE USED

Spread sheet Kanban Burndown

Subversion CruiseControl.Net Skype Email

24

CAN WE DO BETTER?

Educate the Product Owner/More PO involvement

Release by chapter Include automated check to CI …

25

WHAT WE LEARNED

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

26

QUESTION?

Bill: bill.li@ScrumChina.com Daniel: tengzhenyu@gmail.com

Jackson: zbcjackson@gmail.com Stone: choushi@gmail.com 27

28

Thanks