TROPICAL AGILEJohannes Brodwall

“How long will it take to drive to Chicago”

“How long will it take to drive to Chicago”

Kandy

t = s/v

After 1 hours, we have only got to Mahara…

Tropical Agile

Presentasjonstittel11

TROPICAL AGILE

Planning – man-week sized items Gather “everyone” to discuss => usage flow Usage flow => product backlog Product backlog => time and cost (t = s/v)

Tracking every week Actual production, changes in scope Demonstrations with customers => expectations Progress, scope, expectation/insufficient done-ness => risk

Accelerating with demo Practice mock demo during planning Use demo driven work to focus on feature slices (avoid deps) Demonstrate with externals to get feedback

Planning

Getting the flow

For some stakeholderWho wants to achieve some goal

The ??? system Is a type of application

Which lets them perform some actions.Unlike most relevant alternative

Our product has some advantage

For companiesWho wants to get specialist work done

The TempEmp system Is a self-serve web application

Which lets them post positions and evaluate candidates.Unlike calling a workforce agent

Our product gives access to more talent in a structured way.

(rough number) of(stakeholder type)

use our system (frequency)to (perform task) * X.

They want the system to be (quality attribute).

Hundred of client HR managers use our system several times per week to post positions,

evaluate candidates, and select candidates. They want the system to let them specify their exact

requirements.

Thousands of workers use our system every few months to enter and update their skill profile and

every week to register hours. They want the system to be easy to use.

A few handfulls of case workers use our system every day to suggest candidates for positions. They want the system to be fast and efficient.

A handful of key account managers use our system every few weeks to add new client

companies. They want the system to simple and intuitive .

A handful of account managers use our system every week to bill client companies and follow up

missing payments. They want the system to automated.

1. KAM adds new client company

2. Client HR manager posts positions

3. Worker register skill profile

4. Case worker suggests candidate for position

5. Client HR manager evaluates candidate

6. Client HR manager selects candidate

7. Worker works

8. Worker register hours

9. Account manager bills client company

10. Client company pays

11. Account manager follows up missing payment

Producing the log

1. …

2. Client HR manager posts positions

3. …

4. Case worker suggests candidate for position

5. …

6. …

1. Experimental post position

2. …

3. …

4. …

5. Simplified post position

6. …

7. …

12. …

13. Complete post position

14. …

15. …

27. Polished post position

28. …

…

58. …

1. …

2. Client HR manager posts positions

3. …

4. Case worker suggests candidate for position

5. …

6. …

1. Experimental post position

2. …

3. Experimental suggest candidate

4. …

5. Simplified post position

6. …

7. …

12. Simplified suggest candidate

13. Complete post position

14. …

27. Complete suggest candidate

28. Polished post position

29. …

…

58. …

1. …

2. Client HR manager posts positions

3. …

4. Case worker suggests candidate for position

5. …

6. …

1. Experimental post position

2. Simplified deployment

3. Experimental suggest candidate

4. …

5. Simplified post position

6. …

7. …

12. Simplified suggest candidate

13. Complete post position

14. …

27. Complete suggest candidate

28. Polished post position

29. Automated deployment

…

58. …

• Look and feel

• Deployment

• Performance

• Quality

• …

1. …

2. Client HR manager posts positions

3. …

4. Case worker suggests candidate for position

5. …

6. …

1. Experimental post position

2. Simplified deployment

3. Experimental suggest candidate

4. Simple look and feel

5. Simplified post position

6. …

7. First performance test

12. Simplified suggest candidate

13. Complete post position

14. …

27. Complete suggest candidate

28. Polished post position

29. Automated deployment

…

58. …

• Look and feel

• Deployment

• Performance

• Quality

• …

Tracking the project

Week Ends Planned Σ planned

1 17. Apr 6 6

2 24. Apr 6 12

3 1. May 4 16

4 8. May 6 22

5 15. May 6 28

6 22. May 6 34

7 29. May 6 40

8 5. Jun 6 46

9 12. Jun 6 52

10 19. Jun 6 58

Ends Plan Σ planned Σ hours Hours Johannes Jan Ole Bjørn1 17. Apr 6 6 150 150 37.5 37.5 37.52 24. Apr 6 12 300 150 37.5 37.5 37.53 1. May 4 16 420 120 30 30 304 8. May 6 22 570 150 37.5 37.5 37.55 15. May 6 28 490 120 30 30 306 22. May 6 34 640 150 37.5 37.5 37.57 29. May 6 40 760 120 30 30 308 5. Jun 6 46 910 150 37.5 37.5 37.59 12. Jun 6 52 1100 150 37.5 37.5 37.510 19. Jun 6 58 1300 150 37.5 37.5 37.5

Running project

Tracking the project

Week 1

Week 2

Week 3

Week 4

Week 5

Week 6

Week 7

Week 8

Week 9

Week 10

Week 11

0

20

40

60

80

100

120

DoneTotal

Story Planned week

Forecast Actual

Experimental post position 1 17. Apr 15. Apr

Simplified deployment 1 17. Apr 15. Apr

Experimental suggest candidate

1 17. Apr 17. Apr

…

Simplified post position 3 1. May

…

Simplified suggest candidate 4 8. May

Complete post position 4 8. May

…

Complete suggest candidate 5 15. May

Polished post position 5 15. May

Automated deployment 5 15. May

Week Ends Planned Σ planned Actual Σ actual

1 17. Apr 6 6 6 6

2 24. Apr 6 12 6 12

3 1. May 4 16

4 8. May 6 22

5 15. May 6 28

But what if you’re wrong?

Week Ends Planned Σ planned Actual Σ actual

1 17. Apr 6 6 6 6

2 24. Apr 6 12 6 12

3 1. May 4 16 2 14

4 8. May 6 22

5 15. May 6 28

Story Planned week

Forecast Actual

Experimental post position 1 17. Apr 15. Apr

Simplified deployment 1 17. Apr 15. Apr

Experimental suggest candidate

1 17. Apr 17. Apr

…

Simplified post position 3 1. May 8. May

…

Simplified suggest candidate 4 8. May

Complete post position 4 8. May

…

Complete suggest candidate 5 15. May

Polished post position 5 15. May

Automated deployment 5 15. May

Week Ends Planned Σ planned Actual Σ actual

1 17. Apr 6 6 6 6

2 24. Apr 6 12 6 12

3 1. May 4 16 2 14

4 8. May 6 22 9 23

5 15. May 6 28

Story Planned week

Forecast Actual

Experimental post position 1 17. Apr 15. Apr

Simplified deployment 1 17. Apr 15. Apr

Experimental suggest candidate

1 17. Apr 17. Apr

…

Simplified post position 3 1. May 8. May

…

Simplified suggest candidate 4 8. May 8. May

Complete post position 4 8. May 8. May

…

Complete suggest candidate 5 15. May 8. May

Polished post position 5 15. May

Automated deployment 5 15. May

Week Ends Planned Σ planned Actual Σ actual

1 17. Apr 6 6 6 6

2 24. Apr 6 12 6 12

3 1. May 4 16 2 14

4 8. May 6 22 9 23

5 15. May 6 28 10 33

Crazy and untested

Story How good? How useful?

Experimental post position 3 2

Simplified deployment 3 3

Experimental suggest candidate

3 2

…

Simplified post position 3 5

…

Simplified suggest candidate 5 4

Complete post position 4 4

…

Complete suggest candidate

Polished post position

Automated deployment

Week Ends Actual Σ actual Quality Last release

1 17. Apr 6 6 4,0

2 24. Apr 6 12 3,2

3 1. May 4 16 3,8 1. May

4 8. May 6 22 3,7 1. May

5 15. May 6 28 2,3 1. May

Week Ends Team 1 Σ team 1 Team 2 Σ team 2

1 17. Apr 6 6 10 10

2 24. Apr 6 12 10 20

3 1. May 4 16 8 28

4 8. May 6 22 10 38

5 15. May 6 28 10 48

Presentasjonstittel46

TROPICAL AGILE

Planning – man-week sized items Gather “everyone” to discuss => usage flow Usage flow => product backlog Product backlog => time and cost (t = s/v)

Tracking every week Actual production, changes in scope Demonstrations with customers => expectations Progress, scope, expectation/insufficient done-ness => risk

Accelerating with demo Practice mock demo during planning Use demo driven work to focus on feature slices (avoid deps) Demonstrate with externals to get feedback

Presentasjonstittel47