2. 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 2Agile Mëtteg - Agile Tooling
3. LET’S GET TO KNOW EACH OTHER
11 November 2010 Agile Mëtteg - Agile Tooling 3
4. 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 Agile Mëtteg - Agile Tooling 4
IS users
Service
s
Software
Development
&
Software
Maintenance
IS
Solution
s
IS
Service
s
6. PARTICIPANTS
Who are you?
What is your role?
What do you know about agility?
What are your expectations?
11 November 2010 6Agile Mëtteg - Agile Tooling
8. ADAPTATION vs. ANTICIPATION
Source: Succeeding with Agile: Software Development using Scrum, Mike Cohn , Addison-Wesley, 2009
11 November 2010 8Agile Mëtteg - Agile Tooling
9. MEET THE FUD
11 November 2010 9Agile Mëtteg - Agile Tooling
Fear, Uncertainty and Doubt
10. QUALITY STRIKES BACK!
11 November 2010 10Agile Mëtteg - Agile Tooling
Quality is the best answer to FUD
Deliver quality items faster than before
Win trust
Easier said than done?
11. OBJECTIVES
Build knowledge
Build a solution that fits the real needs
Optimize delivered value
Build trust relationship
11 November 2010 Agile Mëtteg - Agile Tooling 11
12. WHICH QUALITY & HOW TO MEASURE
IT?
11 November 2010 12Agile Mëtteg - Agile Tooling
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
13. IN THE MEANTIME…
11 November 2010 13Agile Mëtteg - Agile Tooling
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
14. SO WHERE DOES QUALITY SIT?
11 November 2010 14Agile Mëtteg - Agile Tooling
Delivered features (value) must be target
constant and (very) high quality
15. Trust is a key asset to Agility adoption
11 November 2010 15Agile Mëtteg - Agile Tooling
If people trust Agile teams/initiative,
adoption is (of course) easier
17. 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 Agile Mëtteg - Agile Tooling 17
Source: http://www.agilemanifesto.org/
18. 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 Agile Mëtteg - Agile Tooling 18
Source: http://www.agilemanifesto.org/
19. 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 Agile Mëtteg - Agile Tooling 19
20. 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 Agile Mëtteg - Agile Tooling 20
21. AGILE PROCESS
11 November 2010 Agile Mëtteg - Agile Tooling 21
Priority
Needs
Iterations System in progress
Iterative and incremental process
Adaptive planning
Iterations time-boxed
23. TOOLS EVERYWHERE
Frequent delivery AND Continuous
Integration to enforce and ease this
delivery
11 November 2010 Agile Mëtteg - Agile Tooling 23
24. 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 Agile Mëtteg - Agile Tooling 24
25. 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 Agile Mëtteg - Agile Tooling 25
26. 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 Agile Mëtteg - Agile Tooling 26
27. TOOLS IN THE AGILE I.T.
11 November 2010 Agile Mëtteg - Agile Tooling 27
28. 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 Agile Mëtteg - Agile Tooling 28
29. CUSTOMER-FOCUSED AGILE TOOLS
Transparency and collaboration tools
WIKI
DSLs (Ubiquitous language)
Wallboards or Equivalent virtual Dashboards
11 November 2010 Agile Mëtteg - Agile Tooling 31
30. 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 Agile Mëtteg - Agile Tooling 32
31. 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 Agile Mëtteg - Agile Tooling 33
33. 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 Agile Mëtteg - Agile Tooling 35
34. 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 Agile Mëtteg - Agile Tooling 36
36. SALESFORCE.COM
Source: Greene and Fry 2008. Moutain Goat Software, LLC
568% more
value
delivered in
the first year
of being agile.
11 November 2010 38Agile Mëtteg - Agile Tooling
37. SATISFACTION
Improved
Significantly
Improved
Enhanced ability to manage
changing priorities
41% 51%
Improved project visibility 42% 41%
Improved alignment of IT
and business goals
39% 27%
Reduced project risk 48% 17%
Source: VersionOne, 2008 State of Agile Development Survey
11 November 2010 39Agile Mëtteg - Agile Tooling
39. HOW WE CAN HELP
11 November 2010 Agile Mëtteg - Agile Tooling 41
New to Agile?
Want to get
started?
Already in?
Awareness
sessions
Trainings and Certifications
Assistance &
Support
Coaching
Diagnostic
« Quick Scan »
Agile
Agile « Jump
Start » &
transition
Agile « Health
Check »
40. Certifications Duration Date
Certified Scrum Master 2 days To plan in
2011
Certified Scrum Product Owner 2 days To plan in
2011
NEXT TRAININGS & CERTIFICATIONS
Courses Duration Nov Dec Jan
iPhone development 5 days 22 - -
Software factory 3 days - 08 12
Agile methods 1 day 08 13 10
Scrum 2 days 09 14 11
11 November 2010 Agile Mëtteg - Agile Tooling 42
Complete calendar on: http://www.agilepartner.net/training/focus-on/