You are on page 1of 32

Agile process in

Thoughtworks

One iteration
Iteration
kick of

Showcas
e

Retrospe
ct

Iteration
plan

Dev Test
Integrati
on

Iteration Kick off


Meeting

Iteration Kick of Meeting

PM/DPM
+
PO

Iteration Kick of Meeting

Review the backlog


Figure out high priority tasks
Feedback
Story time (sometimes)

A new iteration

comes

Iteration Plan Meeting

Iteration Plan Meeting


Whole dev team together
Two weeks == An
iteration
20-25 points
Prioritize tasks in advance
Brief tasks

Iteration Plan Meeting

Evaluate by 1, 2, 3, 5, 8 point
Stop when about 20 points in plan
Dev team decide the plan
Last for 1 hour
Dont change during iteration

Development

Daily scrum meeting

Pair Programming & TDD

TDD

Code review

A day in iteration

Stand meeting

Pairing, TDD
1 WIP 1 pair

Code review

communication

One team one position


Real time communicate
Always-on camera
BA, developer work together
Rotate modules
Last min to fill card

Coding progress

Pairing & Rotating


Be aware of whole project
TDD & automatic testing
Dependency management with PM
Setup infrastructure though CM tools
Consistency for local and server
Phoenix like and isolated local environment

Consistency - workspace

Consistency dev/test/prod

Consistency local dev env

Testing

Testing

One command testing


Prepush testing
Unit testing,
acceptance testing,
e2e testing
Style checking:
checkstyle, jsLint
Testing before
building

capybara

Build package

Every module built into a rpm


Use rpm to reflect module dependencies

Deployment

Automatic deployment
Keep high consistency
Dont setup manually
One command setup from scratch

Release

Small release

Every commit should be tested fully


Every code commit should not fail any test
case
Dev/Test/Prod should be in high consistency
All environment should be easy to reset and
configured to a specific state

Showcase

Retrospective

Team

One team one position


No cross time zone if possible
Multiple scrum team by modules
Team should be aware of all modules

You might also like