Ketter Tuotanto

Agile Production model aka KetTuWhat in the name of Fox(ility)?@ToivoVaje#ElisaAppelsiini #KetTumalli

1

2Overview

What does Elisa Appelsiini do?

Platform services, infrastructure

Roadmap, data center, ITIL. All kinds of IT services.4

Business IT servicesDevelopmentUpgradesAsset managementSecurity solutionsManagement-infra

ManagementMaintenanceSupportsContinuous Development

IntegrationsSolutionsIntegrationsIntegration projectsMicrosoft BizTalkConsultingAuditsMappingsStrategic planning

Multiple customersTight deadlinesComplex systems6Its a tough job...

The Agile Production Model

8Agile Production Model KetTu (or Foxility)

How the framework was born.

8

9

10KetTu from the Helicopter: Lean Teams

Our Agile teams are called Lean teams.Members include Technical Product Owner (TPO) and a group of experts.Each customer also has a dedicated Service Manager.

10

11(Technical) Product Owner

Prioritizes the teams Backlog (work queue)Acts as a customer simulator for the teamInterprets customer needs into an implementable formRepresents team towards customer and the rest of the organization

11

Architects, developers, testers, designers, UX and other expertsDecide HOW something is implementedFreedom to choose technologies and models within the given limitsWith freedom comes responsibilityTransform user stories and change requests to a form that fulfills Definition of DoneSelf-organizing12Development Team

Kept in JIRATransparently available to everyoneIncludes all the work team is handling13Backlog

Base level agreed across all projectsAll work that is Done, must fulfill DoDIn the correct branch in version controlTestedReviewedDocumentedetc.14Definition of Done (DoD)

Retrospectives are integrated to the daily workRegular check-ups on how to improve the working practices15Continuous Learning & Improvement

16Technical teams

People in similar role belong to technical teamsTeams are responsible for staying at the cutting edge of technologyCommunities of Practice

17Once upon a Sprint...

Brief introduction to iterative and incremental development.17

18Planning the amount of work

Team agrees on the amount of work it conciders feasible for the given time frame. Then they form a plan how to make it real and the sprint is started.18

19JIRA Workflow States

In the beginning everything is in the leftmost column. Because the team mostly does pair-programming, theres no need to have a separate column for code reviews. The team also includes a full-time tester, so the communication happens naturally and this doesnt either need to be done via the board. In practice the stages are thus To Do, In Progress and Done. In practice, theres usually need to have more stages, because tester and customer might not be involved full-time.19

20Dailys

Team tells each other what they have done, what they intend to do and if something is holding them back. This is the moment to raise the flag and ask for peer support.20

21Demo / Review

The Team presents the results to TPO/customer. While this is done, understanding is built on how well the solution fits the original need.This is also the moment to examine how much was actually accomplished compared to what was planned. This is the teams velocity and can be used to forecast capacity for next sprint.21

22Lessons Learned / Retro

Team improves their way of working. What worked and should be done also in the future and what they should differently in the next sprint?Team decides what they will commit on improving next.22

We do difficult things in complex environmentsOur model enables our experts toorganize their own workown their resultssupport one anotherWe continuously learn from experience23Recap

Thank you!@ToivoVaje#ElisaAppelsiini #KetTumalli