Agile Mëtteg series session 9

Agile Tooling
Agile Mëtteg– November 11th, 2010

OBJECTIVES & AGENDA
Objectives
Get a short introduction to agile tooling, and where it sits next to agile methods and practices
Agenda
Agility and Quality
Tools contribution to Agile software development
Tools in the Agile IT
(Examples)
To conclude
11 November 2010
2
Agile Mëtteg - Agile Tooling

Let’s get to know each other
11 November 2010
3

AGILE PARTNER SERVICES
Custom Software Development & Maintenance
Our core business to answer customer needs
IS services
Thanks to our expertise we can support IT team to reach their productivity & quality objectives (Assessment, Coaching, Support, Training, Resource delegation…)
IS Solutions
Take benefit from commercial or Open Source platform to answer as quick as possible to specific needs
IS users services
We can support Product & Services owners to work closely with the IT team (Assessment, Coaching, Support, Training, Resource delegation…)
11 November 2010
4
IS users Services
1
4
Software Development & SoftwareMaintenance
2
ISSolutions
IS Services
Agility
Agility
3
1
2
3
4
Agility

SPEAKER
11 November 2010
5
Agile Practitioner
Lean/Kanban, Devops

PARTICIPANTS
Who are you?
What is your role?
What do you know about agility?
What are your expectations?
11 November 2010
6

AGILITY AND QUALITY
11 November 2010
7

ADAPTATION vs. ANTICIPATION
Source: Succeeding with Agile: Software Development using Scrum, Mike Cohn , Addison-Wesley, 2009
11 November 2010
8

MEET THE FUD
11 November 2010
9
Fear, Uncertainty and Doubt

QUALITY STRIKES BACK!
11 November 2010
10
Quality is the best answer to FUD
Deliver quality items faster than before
Win trust
Easier said than done?

OBJECTIVES
Build knowledge
Build a solution that fits the real needs
Optimize delivered value
Build trust relationship
11 November 2010
11

WHICH QUALITY & HOW TO MEASURE IT?
11 November 2010
12
Agile is about adding Value
Giving value to a customer for a product
Contributing to a value stream
Focusing on value
Enforces removal of impediments
Makes evaluation obvious from clients to I.T. teams to Management
Gives shared quality goals for everybody

IN THE MEANTIME…
11 November 2010
13
Many people won’t see things this way
Non Agile boundaries exist:
Audit constraints
Input from non-agile teams
Output to non-agile teams
And moreover:
Agile doesn’t mean messy nor improvised development
Agile doesn’t mean costless development
Agile means focus on value

SO WHERE DOES QUALITY SIT?
11 November 2010
14
Delivered features (value) must be target constant and (very) high quality

Trust is a key asset to Agility adoption
11 November 2010
15
If people trust Agile teams/initiative, adoption is (of course) easier

Tools contribution to Agile SDLC
11 November 2010
16

THE 4 VALUES
Extract from Manifesto for Agile Software Development:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
11 November 2010
17
Source: http://www.agilemanifesto.org/

THE 4 VALUES
Extract from Manifesto for Agile Software Development:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
11 November 2010
18
Source: http://www.agilemanifesto.org/

EXTRACT FROM THE 12 PRINCIPLES
Satisfy the customer through early and continuous delivery of valuable software.
Deliver working software frequently with a preference to the shorter timescale.
Simplicity--the art of maximizing the amount of work not done--is essential.
Business people and developers must work together daily throughout the project.
Face-to-face conversation for conveying information to and within a development team.
11 November 2010
19

EXTRACT FROM THE 12 PRINCIPLES
Satisfy the customer through early and continuous delivery of valuable software.
Deliver working software frequentlywith a preference to the shorter timescale.
Simplicity--the art of maximizing the amount of work not done--is essential.
Business people and developers must work together daily throughout the project.
Face-to-face conversation for conveying information to and within a development team.
11 November 2010
20

AGILE PROCESS
11 November 2010
21
Needs
System in progress
Iterations
Priority
Iterative and incremental process
Adaptive planning
Iterations time-boxed

TOOLS EVERYWHERE
A Whiteboard/KanbanAND a good ticketing system
11 November 2010
22

TOOLS EVERYWHERE
Frequent delivery AND Continuous Integration to enforce and ease this delivery
11 November 2010
23

TOOLS EVERYWHERE
TDD AND Testing frameworks,
Collaboration tools for User Acceptance Tests
Good IDEs/Editors for Efficient Refactoring
Good code analysis for fast error analysis
11 November 2010
24

TOOLS TO IMPROVE YOUR PROCESS
Tools in an Agile project/context are not focused on nor chosen for their compatibility with a predefined process
Tools should adapt to your needs and assist you in improvements of your process
Development process
Testing process
Validation process
Release process
11 November 2010
25

TOOLS TO AUGMENT YOUR FOCUS
Tools should help you improve quality, by removing boiler-plate and helping you focus on Value
Tools should evolve constantly with your process
11 November 2010
26

TOOLS IN THE AGILE I.T.
11 November 2010
27

MORE THAN JUST PROJECTS
SDLC (Software Development Life-Cycle) expands to more than a development team
How do Agile tools help with customer interaction?
How does Agility integrate with (for example) ITIL?
How can Agility ease interaction with operations?
11 November 2010
28

THE CUSTOMER IS EXPECTED TO
Evolve from Project to Product Management
Elaborate and share a vision
Manage product lifecycle with Releases
Understand and communicate the requirements
Evaluate business value
Have the power and responsibility to decide
Be available to collaborate with the team continuously
Respect team capacity limit
11 November 2010
29

THE CUSTOMER CAN EXPECT THE TEAM TO
Estimate effort (on a relative scale)
Commit for achieving short-term goals
Build quality in
Accept changes in requirements
Improve continuously
11 November 2010
30

CUSTOMER-FOCUSED AGILE TOOLS
Transparency and collaboration tools
WIKI
DSLs (Ubiquitous language)
Wallboards or Equivalent virtual Dashboards
11 November 2010
31

ITIL AND AGILITY
ITIL, as many frameworks and methods, comes with methods and tools (remember the manifesto?)
ITIL should be considered a good grammar, though it doesn’t provide value by itself
Value should still be the main goal, and ITIL a shared vocabulary/tool to achieve it
This is true for any other (imposed) classic framework or method
11 November 2010
32

OPERATIONS AND AGILITY
A new trend: Dev/ops
Limit between development and operations blurrier every day
Cloud and virtualization are helping this
frequent releases have their impact
End-to-end Delivery quality attempted very early, and therefore achieved very early!
Failure is allowed, though quality and tooling ensure easy fixes (reverting to former version in a click…)
11 November 2010
33

CONCLUSION
11 November 2010
34

TOOLS SHOULDN’T GET IN THE WAY
Everything that disallows providing more value with more quality faster should be considered an impediment
This is also true for tools.
11 November 2010
35

Tools should help improve the process
Tools should be there to help and assist the process
Tools should adapt to process improvements or be abandoned
Tools should not drive the process, people and value (stream) should
11 November 2010
36

TIME-TO-MARKET
Sources: Mah 2008. Moutain Goat Software, LLC
11 November 2010
37

SALESFORCE.COM
568% more value delivered in the first year of being agile.
Source: Greene and Fry 2008.Moutain Goat Software, LLC
11 November 2010
38

SATISFACTION
Source: VersionOne, 2008 State of Agile Development Survey
11 November 2010
39

QUESTIONS
40
11 November 2010
READY to TRY

HOW WE CAN HELP
11 November 2010
41
New to Agile?
Want to getstarted?
Already in?
Awarenesssessions
Assistance & Support
Coaching
Trainings and Certifications
Diagnostic « Quick Scan » Agile
Agile « Jump Start » & transition
Agile « Health Check »

NEXT TRAININGS & CERTIFICATIONS
11 November 2010
42
Complete calendar on: http://www.agilepartner.net/training/focus-on/

RESOURCES
Agile Partner: www.agilepartner.net
NEW!blog.agilepartner.net
Agile Interest Group Luxembourg:www.aiglu.org
Agile Alliance: www.agilealliance.org
Scrum alliance: www.scrumalliance.org
Scrum.org
11 November 2010
43

CONTACTS
Thank You
11 November 2010
44

Agile Mëtteg series session 9

by Agile Partner S.A. on Nov 11, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

2 Embeds 69

Statistics

Agile Mëtteg series session 9 — Presentation Transcript

http://blog.agilepartner.net	55
http://www.agilepartner.net	14