Agile Development TECH STARTUP

BY RATTAKORN POONSUPH, D.SC.

Business Transformation – recent decades

Traditional

Digital

©X.Rattakorn

Why’ change?

Globalization

Mobile & Internet of Things

Digital Transformation

Why Agile?

20 Century (old model)

Nowadays

Manufacturing, Construction Software, Finance, Health-care

We know about what’ we try to accomplish?

Predictable / Repeatable works

Uncertainty, Change Rapidly

Only learning organization, can keep up the futures.

Startup / New Product Dev. Legacy Org. / Known product.

Waterfall model

The unmodified “waterfall model”. Progress flows from the top to the bottom, like a waterfall.

This approach is highly risky, often more costly and

generally less efficient than Agile approaches

REQUIREMENTS

DESIGN

DEVELOPMENT

Verification

MAINTENANCE

Takes too long

Changes

Skipped You don’t realize any value until the end of the project You leave the testing until the end You don’t seek approval from the stakeholders until late

in the day

But…

Waterfall model : Fail – late lifecycle

AGILE Iterative

Adaptable Rapid

Cooperative Quality-driven

Not a process, it's a philosophy or set of values

Agile Approach Adaptive, empirical process

Small repeating cycles

Short-term planning with constant feedback, inspection and adaptation

Fail-early lifecycle

Agile vs. Waterfall

REQUIREMENTS

DESIGN

DEVELOPMENT

TESTING

MAINTENANCE

Iterative Agile

Agile Umbrella

Agile

Crystal

XP Scrum DSDM

FDD

Kanban RUP

RUP (120+)

XP (13)

Scrum (9)

Kanban (3)

Do Whatever!! (0)

More Prescriptive

More Adaptive

and few more…

* Check wikipedia for list of all Agile methods

RUP has over 30 roles, over 20 activities, and over 70 artifacts

more rules to follow

fewer rules to follow

Agile approach : Fail-early lifecycle

Fix TIME and BUDGET.

Scrum A light-weight agile process tool

Split your organization into small,

cross-functional, self-organizing teams.

Split your work into a list of small, concrete deliverables. Sort the list by priority

and estimate the relative effort of each item.

Scrum Team

Scrum Master

Product/ Project Owner

Split time into short fixed-length iterations/ sprints (usually 2 – 4 weeks), with

potentially shippable code demonstrated after each iteration.

Scrum (contd..)

January May

Optimize the release plan and update priorities in collaboration with the customer,

based on insights gained by inspecting the release after each iteration.

Optimize the process by having a retrospective after each iteration.

Agile Development (Scrum) So instead of a large group spending a long time building a big thing, we have a

small team spending a short time building a small thing.

But integrating regularly to see the whole.

Agile Performance Measurement