Effective use of Agile

1. Agile Efficacy
Effectiveness of Agile

2. Some facts based on studies
Only 40% of projects meet schedule, budget, and quality goals. (IBM study)
On average, most IT projects run 45% over budget and 7% over time, while delivering 56%
less value than predicted. (McKinsey & Co., in conjunction with the University of Oxford)
On more statistics states: “Most analyses conclude that between 65 and 80% of IT projects
fail to meet their objectives, and also run significantly late or cost far more than planned.”
One Canadian study stated: “Bad communications between parties are the cause of IT project
failures in 57% of cases they studied.”

3. Requirements Gap
Collaboration Gap
Communication Gap
Why software projects fail

4. It was often futile for the business to try to
develop complete requirements upfront, and
as a result there were many problems that
resulted from customer not getting what they
needed or wanted. I knew there had to be a
better way than to think we could look into a
crystal ball in product development.
- Tom Meller

5. Agile - the better way

7. Highlights of Agile Development
Iterative Development
Quick review
Tested Delivery
Frequent Feedback
Collaboration
Communication
Usable
Software
Customer
Collaboration
Responding to
change

8. Benefits Of Agile Adoption
www.clariontechnologies.co.in8
Engagement
Transparency
Frequent
Delivery
Predictability
Flexibility
Business &
Customer
Focus
High Quality
Provides more opportunities for the team
to truly understand the client’s vision
Provides a unique opportunity for clients to be
involved throughout the project, from prioritizing
features to iteration planning and review sessions
By using time-boxed, fixed schedule Sprints of 1-4
weeks, new features are delivered quickly and
frequently, with a high level of predictability. This
also provides the opportunity to release or beta test
the software earlier than planned if there is
sufficient business value.
Because each Sprint is a fixed duration, the
cost is predictable and limited to the
amount of work that can be performed by
the team in the fixed-schedule time box
Provides the opportunity to introduce
changes within a few weeks
By allowing the client to determine the priority
of features, the team understands & deliver
the features that provide the most business
value. Users can beta test software after each
Sprint, gaining valuable feedback early.
Breaking down the project into manageable
units, the project team can focus on high-quality
development, testing, and collaboration.

9. Agile Overcomes The Challenges
www.clariontechnologies.co.in9
• I should be able to see what
Business values is getting
delivered.
Business
Value
• When can I see my requirements
coming to life? When can I put it
to release?
Visibility
• What if I have an urgent
unplanned requirement?Adaptability
I get the tested features actually
deliver business value, that too every
few weeks.
I can review and UAT a working
product every few weeks!
My high priority business requests
always gets executed first,
irrespective of initial plan.

10. Agile Overcomes The Challenges
www.clariontechnologies.co.in10
• How can quality be built in right
from the start?Quality
• What if it does not turn out as
expected after waiting so long?Risk
• Can the multi-located teams
collaborate effectively?Collaboration
I can get the quality baked-in from
the start of the project.
I can plan my releases and know
associated risks well in advance.
My Team and I collaborate effectively
to ensure communication is
maximized.

11. Agile Frameworks
www.clariontechnologies.co.in11
Scrum
Kanban
Scrumban

12. Scrum Process
• Focus on delivering the highest business value in the shortest time of the
sprint.
• The business sets the priorities of the work.
• The self-organized team determines the best way to deliver the prioritized
work.
• Every sprint (1-4 weeks) Product owner can see real working software
(production ready).
• The stakeholders can make a decision on when to push it out for production
release.
• Everyday customer involvement (15 mins) facilitates better alignment.
www.clariontechnologies.co.in12

13. Clarion Scrum Process
www.clariontechnologies.co.in13
Information Radiator
Online Scrum Tool
Cross-functional
scrum team
WORK ITEM 1
WORK ITEM 2
WORK ITEM 3
WORK ITEM 4
WORK ITEM 5
WORK ITEM 6
PRODUCT BACKLOG
WORK ITEM 1
WORK ITEM 2
WORK ITEM 3
SPRINT BACKLOG
TASK
TASK
TASK
TASK
TASK
TASK
TASK
TASK
TASK
TASK
TASK
TASK
TASK
TASK
TASK
PRODUCT
INCREMENT
Sprint
Preplanning
Sprint
Zero
Sprint Planning
Meeting
Daily
Scrum
Meeting
Sprint
Review
Meeting
Sprint
Retrospective
Meeting
Design Code
Analysis
Deploy Test
CI
Scrum
Master
PO PO
Product
Backlog
Grooming

14. Kanban
• Best for projects in Maintenance
• Visualize your work in hand
• Limit work in progress. One at a time.
• Don't push too hard. Pull!
• Use, monitor, adapt and improve
• Workflow is inherently visible.
• Development process is divided into
columns/stages.
• Cumulative flow chart shows relative amount
of work in each stage.
www.clariontechnologies.co.in14

15. Scrumban
• An Agile management methodology describing hybrids of Scrum and Kanban.
• The iteration review and planning cycle happens just as in Scrum.
• The goal of planning is to fill the slots available, not fill all of the slots. i.e. sprint
capacity is not exhausted.
• Accommodates the production tickets on flexible priority basis.
www.clariontechnologies.co.in15

16. Methodology Selection
www.clariontechnologies.co.in16
Scrum
• Enterprise maturity for teams working on product.
• Project with new development mostly.
Kanban
• Support and maintenance teams.
• Continuous product development.
Scrumban
• Startups, fast-pace projects.
• Maintenance plus development tasks.

17. Customer Involvement Is A Must!
• Availability: Daily involvement minimum 15 mins
• Product Owner from customer end, Shadow Product Owner from Clarion
• Agile coach from Clarion
• Frequent Review & Feedback per sprint
www.clariontechnologies.co.in17

18. Clarion Proficiency
• Certified Scrum Master and Agile Coach
• Agile Trained Team
• Great success record
• Proven process
• Dedicated COE team
• Proficiency in other Agile methodologies such as Kanban & Scrumban
www.clariontechnologies.co.in18

19. “"Overall very good, consistent support & reliable
development, with strong management of IT development.
Transition to Agile Development approach has been very
helpful in quantifying how much we are able to achieve on a
weekly basis to understand timelines on key deliverables.”
Mark Hall
CEO, G8Way Healthcare Payments
www.clariontechnologies.co.in19

20. Thank You!