TROPICAL AGILE Johannes Brodwall

“How long will it take to drive to Chicago”

Kandy

t = s/v

After 1 hours, we have only got to Mahara…

Tropical Agile

TROPICAL AGILE 11 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 Presentasjonstittel

Planning

Getting the flow

For some stakeholder Who 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 companies Who 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

WeekEndsPlannedΣ planned 117. Apr Apr May May May May May Jun Jun Jun658

EndsPlanΣ planned Σ hoursHoursJohannesJan OleBjørn 117. Apr Apr May May May May May Jun Jun Jun

Running project

Tracking the project

StoryPlanned week ForecastActual Experimental post position117. Apr15. Apr Simplified deployment117. Apr15. Apr Experimental suggest candidate 117. Apr … Simplified post position31.May … Simplified suggest candidate48. May Complete post position48. May … Complete suggest candidate515. May Polished post position515. May Automated deployment515. May

WeekEndsPlannedΣ plannedActualΣ actual 117. Apr Apr May May May628

But what if you’re wrong?

WeekEndsPlannedΣ plannedActualΣ actual 117. Apr Apr May May May628

StoryPlanned week ForecastActual Experimental post position117. Apr15. Apr Simplified deployment117. Apr15. Apr Experimental suggest candidate 117. Apr … Simplified post position31.May8. May … Simplified suggest candidate48. May Complete post position48. May … Complete suggest candidate515. May Polished post position515. May Automated deployment515. May

WeekEndsPlannedΣ plannedActualΣ actual 117. Apr Apr May May May628

StoryPlanned week ForecastActual Experimental post position117. Apr15. Apr Simplified deployment117. Apr15. Apr Experimental suggest candidate 117. Apr … Simplified post position31.May8. May … Simplified suggest candidate48. May Complete post position48. May … Complete suggest candidate515. May8. May Polished post position515. May Automated deployment515. May

WeekEndsPlannedΣ plannedActualΣ actual 117. Apr Apr May May May

Crazy and untested

StoryHow good?How useful? Experimental post position32 Simplified deployment33 Experimental suggest candidate 32 … Simplified post position35 … Simplified suggest candidate54 Complete post position44 … Complete suggest candidate Polished post position Automated deployment

WeekEndsActualΣ actualQualityLast release 117. Apr664, Apr6123,2 31.May4163,81.May 48. May6223,71.May 515. May6282,31.May

WeekEndsTeam 1Σ team 1Team 2Σ team Apr Apr May May May

TROPICAL AGILE 46 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 Presentasjonstittel

47