henryjacob.com

Flavours of Agile

henryjacob.com

henryjacob.com

Waterfall

Quick feedback cyclesHigh visibilityEasy to address changesCollaboration

ParallelStructuredStill long feedback cycleStill no visibility Still difficult to address changes Tools and process centric

SequentialVery long feedback cycleNo visibility Difficult to address changes

RUP Agile

henryjacob.com

Agile is not a formula, or a best practice

henryjacob.com

It is a philosophy

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

henryjacob.com

Our highest priority is to satisfy the customer through early and continuous deliveryof valuable software.

Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

Deliver working software frequently, from a couple of weeks to a couple of months, with apreference to the shorter timescale.

Business people and developers must work together daily throughout the project.

Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

It is about principles

henryjacob.com

Working software is the primary measure of progress.

Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

Continuous attention to technical excellence and good design enhances agility.

Simplicity--the art of maximizing the amount of work not done--is essential.

The best architectures, requirements, and designs emerge from self-organizing teams.

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

It is about principles

henryjacob.com

It is a value system

Respect

Courage

Communication

Feedback

Simplicity

Craftspersonship

henryjacob.com

It is a way of thinking

Lean thinking

Add Nothing But Value

Eliminate Waste

Center On The People Who Add Value

henryjacob.com

Based on this philosophy, principles and value system, more specific approaches are explored to address different aspect of software development

henryjacob.com

henryjacob.com

Agile Flavours

Lean Startups for Vision/Entrepreneurship SCRUM/Kanban for ManagementExtreme Programming for EngineeringD3 for Solution Design

http://theleanstartup.com/principleshttp://www.controlchaos.com/http://www.xprogramming.com/xpmag/whatisxp.htmhttp://www.designdrivendevelopment.orghttp://leankit.com/kanban/what-is-kanban/

henryjacob.com

Lean Startups

Project to Product MindsetFocus on MVPValidated LearningBuild-Measure-Learn-PivotContinuous Delivery/Deployment

Design Driven Development (D3)

Design Driven Development (D3) is a simple, proven and agile based approach to build innovative solutions

Design Foundation Design CubeDesign Games

henryjacob.com

Design Driven Development (D3)

Design Driven Development (D3) is a simple, proven and agile based approach to build innovative solutions

Design Foundation Design CubeDesign Games

henryjacob.com

SCRUM

PlanningSprintStandupDemoRetrospective

henryjacob.com

People

(DeveloperTesterSupport)

Customer

Product OwnerSCRUM Master

Team

henryjacob.com

Responsibilities

Developer, Tester, and SupportAdd Value

CustomerVision

Product OwnerRequirement &Release Management

SCRUM MasterFacilitate scrum ceremonies

Remove Impediments

Team

henryjacob.com

SCRUM

Requirement Analysis Sprint

Planning

Product backlog Sprint backlog and Tasks

SprintSprint Demo

Completed functionalities

Retrospective Daily Sprint

New functionalityDefects

henryjacob.com

Artifacts

Product backlog Sprint backlog Sprint Information Sprint Tracking Board

henryjacob.com

Kanban

Visualise WorkLimit Work In ProgressContinuous Improvement

henryjacob.com

Extreme Programming (XP)

Test Driven DevelopmentContinuous IntegrationPair ProgrammingCollective Code OwnershipRefactoring