Being Smart at enterprise agile

The status of agile at Capgemini in the Netherlands
BEING SMART AT ENTERPRISE AGILE

2BEING SMART AT ENTERPRISE AGILE
©2010 Capgemini. All Rights Reserved
Capgemini
 Principal technology officer
 Chief architect Accelerated Delivery Platform
(ADP)
Other
 Author books and articles
 Speaker at international conferences
 Microsoft Partner Advisory Council .NET
 Capping IT Off Blog
 Magazine columns
 Editorial boards & Advisory boards
Web
 www.sanderhoogendoorn.com
 www.smartusecase.com
 Twitter: @aahoogendoorn
 LinkedIn: aahoogendoorn
SANDER HOOGENDOORN

Collaborate
 Different roles, same time (and location)
Iterate
 Two to four weeks iterations
 Plan – Deliver - Evaluate
Deliver
 Small unit of work – smart use cases
 Test early and often
 Early and frequent delivery
Plan
 Plan and measure continuously
Simplify communication
 Simple dashboards, burn down charts
 Pair programming, planning games
WHAT DOES BEING AGILE MEAN?

SCRUM

Where “lightweight” agile isn’t sufficient
CHALLENGES IN ENTERPRISE PROJECTS

Challenges
 Many different stakeholders
 Many external dependencies (availibility)
 Changing requirements
 Many different types of deliverables
 Complex software architectures
Mission impossible
 Difficult to estimate
 Hard to plan
 Tough to build
 Impossible to test
 Thus: extremely high percentages of project
and program failure
CHALLENGES IN ENTERPRISE PROJECTS

COMPLEX IT LANDSCAPES

On implementing enterprise agile
LEVERAGING CAPGEMINI EXPERIENCE

ACCELERATED DELIVERY PLATFORM
Process
Agile
Lifecycle
Smart
Use Cases
Smart
Estimation
Agile
Dashboards
Unified
Testing
Technology
Model driven
development
Reference
Architectures
Frameworks
People
Open
Community
Coaching
Learning

“Regular” projects
 Java
 .NET – Windows, web, Silverlight
Enterprise projects
 Service oriented architecture (SAP SOA)
 Distributed projects (agile co-creation)
Other projects
 Business intelligence
 Re-engineering existing applications
 Application management
 Release management
PROJECT TYPES?

ACCELERATED DELIVERY PLATFORM - SOME REFERENCES
ADP Based
Software Factories
Smart &
Smart Use Cases
(Capgemini) Projects Coaching & Learning

SAP QUALITY AWARD 2010 GOLD WINNER

It’s all about being Smart
DELIVERING IN AN ENTERPRISE AGILE PROCESS

Involve
 Product owner, business users
 Enterprise architects, business analysts
 Application management, operations
 Distributed delivery
Standardize
 Simplify product life cycle
 All roles work on same product
 Model front end and services in smart use cases
 Test and deliver individual services
 Integrate front end and services each iteration
Expect issues
 “Agile is for small projects.”
 “We need to design the whole system up-front.”
 “Sorry. Connectivity to our system will not be available until
January.”
 “We need to review every use case before you can
implement it.”
WHAT DOES ENTERPRISE AGILE MEAN?

SMART
Create
project
proposal
Write
project
plan
Deliver
working
software
Round up
software
Maintain
software

SMART
What product(s) do
we want to deliver?
Define done
Deliver product(s)
using product cycle
Visualise progress
Are we up to speed?
Is our process
optimal?
Are the product(s)
done?

PLAN

BUILD

EVALUATE

Mixing YAGNI and structure
ENTERPRISE AGILE REQUIREMENTS

USER STORIES – APPLES AND PEARS
Often too unstructured
Unsuitable in complex
environments

COMPLEX IT LANDSCAPES

HUGE CASES Hard to build,
impossible to test

A YAGNI approach to requirements
SMART USE CASES

AGILE REQUIREMENTS - APPROACH
D
E
F
Smart
Use Cases
A
Project
Scope
D
Use Cases
A
B C
Hierarchical
Processes
B
D
D
Hierarchical
Processes
Chronological
Processes
Cloud Level Kite Level Sea Level Fish Level
C

CLOUD LEVEL

KITE LEVEL

MODELING SMART USE CASES

WORK IN PROGRESS ...

SOFTWARE ESTIMATION – ABSOLUTE OR RELATIVE?

1. Piece of cake
 Simple selection, simple maintenance
2. Moderate
 Normal selection
3. Average
 Normal maintenance, normal search
4. Hard
 Reporting, one-many
5. Very difficult
 Graphs, extensive reporting, interfacing
8. Extreme, but known
 Complex interfacing
10. Extreme and unknown
 Distributed interfacing, calculations
ABSTRACT WEIGHT OF SMART USE CASES

SMART ESTIMATION POKER

SMART USE CASE STEREOTYPES

Estimating smart use cases
with the whole team

Agile dashboarding for the enterprise
MAKING COMMUNICATION EASY

SMART USE CASE CYCLE
Plan and
prioritize
use cases
Write
test cases
Generate
and build
use case
Run
test cases
Adjust
logic
Define
use case
logic
Accept
use case

SOME STRUCTURE ISN’T BAD

41
Project wall
and dashboard

AGILE DASHBOARDING

AGILE DASHBOARDING - DASHBOARD

AGILE DASHBOARDING – CHANGING STATUS

AGILE DASHBOARDING – BURN DOWN CHART

TESTING SMART USE CASES

BOEHM’S LAW

SMART USE CASE CYCLE
Plan and
prioritize
use cases
Write
test cases
Generate
and build
use case
Run
test cases
Adjust
logic
Define
use case
logic
Accept
use case

RELEASE PLANNING – THE TEST HURDLE

Model activity diagram per use case
 Define which use cases will be tested
 User goal level use cases?
 Sub-function level use cases?
 Models all scenarios in the activity diagram
Identify test scenarios
 Identify decision nodes
 Identify partial paths
 Create full paths from partial paths
 Every path defines a test scenario
Describe test scenarios
 Name partial paths
 Define test scenarios
Write test cases with test scenarios
 Test happy day scenarios
 Test alternative flows

TEST DESIGN FOR INDIVIDUAL SMART USE CASES

Unit testing at the right level
UNIT TESTING SMART USE CASES

Unit test what?
 Methods from the task pattern
 Methods that are called from presentation
 Methods that collaborate with other use cases
 Methods that interact with domain
How?
 Create unit test for each smart use case
 Run methods from smart use case
 Validate outcome (using asserts)
Why?
 Great code coverage
 Regressions testing on smart use cases
 Code generation makes light work

UNIT TESTING SMART USE CASES
Test methods that interact with domain
Set up (in)valid domain object
Run method from use case
Validate outcome

An overview
SMART USE CASE DRIVEN ARCHITECTURE

Presentation
Process
Domain
Data / Services
Outside world
Pages
UserControls
Panels
Use cases
Workflow
Domain objects / Entities
Factories / Repositories
Enums / Value objects / Smart references
[Mapping]
Table Gateways
Queries
[Mapping]
Database

Exact SAP BizTalk Java
Presentation
Process
Domain
Data / Services
Outside world
Pages
UserControls
Panels
Use cases
Workflow
[Mapping]
Service gateways
Service locators
[Mapping]
Services / ESB

Presentation
Process
Domain
Data / Services
Outside world
Service contracts
Operation contracts
Data contracts
Use cases
Services
[Mapping]
Table Gateways / Service Gateways
Queries / Service Locators
[Mapping]
Database
Services / ESB
Exact SAP BizTalk Java

ARCHITECTURE IN CODE
Web
 Pages, controls
Process
 Use cases / Tasks / Flow
Domain
 Factories / Repositories
 Domain Objects / Business rules
 Enums / Value Objects / References
 Search Objects
Data / Services
 Gateways
 Mappings / Describers
Database

An introduction to pragmatic model driven development
GENERATING CODE FROM SMART USE CASES

Forms
Use cases
Domain
objects
Data / Service
classes
Databases
Software Architecture
Tobago
MDA
Test
scenario’s
Frameworks
Specifications
Existing
Applications
Business
models
Domain
Model
Smart
use cases
User interface
specification
1. Map your
business processes
to smart use cases
2. Set up your
domain model
3. Establish
your software
architecture(s)
4. Generate
your code using
a text template
engine
5. Finalize your
application

A SIMPLE SMART USE CASE MODEL

A SIMPLE DOMAIN MODEL
class Budapest.Business
«business class»
Customer
+ Name: string
+ Address: string
+ Postcode: Postcode
+ City: string
+ Country: SmartRef
+ Website: Url [0..1]
«business class»
Contact
+ Name: string
+ Email: Email [0..1]
+ Phone: PhoneNumber [0..1]
+ Department: Departments
«enumeration»
Departments
Sal es
Purchasing
Helpdesk
Management
*

USING TOBAGO MDA

GENERATED CODE IN ASP.NET

Frameworks

Frameworks
 Open extendible architecture
 Many blocks available
 Assemble and generate quickly
 Base applications
 Proven
 In open source!
Blocks
 User interface / Smart binding
 Domain driven design
 Authorization
 Smart use case unit testing
 Resources / multilinguality
 Mapping to databases and services

Community, coaching and learning
PEOPLE

Open community
 Website is a wiki
 Accelerators available for all
 White papers, books
 Software factories
 Agile co-creation
Coaching
 Many engagements in coaching agile
Learning
 Courses available on agile, Smart, smart use
cases, pragmatic UML, smart estimation, agile
software development with ADP
 Custom courses for clients
 Open seminars and workshops
COMMUNITY, COACHING AND LEARNING

www.accelerateddeliveryplatform.com
WWW.SMARTUSECASE.COM

sander.hoogendoorn@capgemini.com
www.sanderhoogendoorn.com
www.smartusecase.com / www.accelerateddeliveryplatform.com
@aahoogendoorn
REFERENCES AND QUESTIONS

Being Smart at enterprise agile

More Related Content

What's hot

Viewers also liked

Similar to Being Smart at enterprise agile

More from Sander Hoogendoorn

Recently uploaded

Being Smart at enterprise agile

Editor's Notes