Agile TRanformation

An Overview of
1 TCS-TigoUne Confidential
A [really] short history of
Software development processes
Waterfall Development
REQUIREMENTS
DESIGN
Waterfall
DEVELOPMENT
Development is
another name for the TESTING
moreTraditional approach to
MAINTENANCE
software development 3 TCS-TigoUne Confidential

Waterfall Development
(contd..)
➔ You complete one phase (e.g. design)

before moving on to the next phase (e.g.
development)
➔ You rarely aim to re-visit a ‘phase’ once
it’s completed. That means, you better get
whatever
you’re doing right the first

time! 4 TCS-TigoUne Confidential
But…
Changes
REQUIREMENTS
You don’t realize any value until

the end of the project. DESIGN
You leave the testing until the
end.
DEVELOPMENT
You don’t seek approval from
the stakeholders until late in Skipped
the day Takes too long
TESTING
This approach is highly risky, often
more costly and generally less
efficient MAINTENANCE
than Agile approaches 5 TCS-TigoUne Confidential

Rapid Adaptable
AGILE Quality-driven
Cooperative Iterative
Not a process, it's a philosophy or set

of values
Agile Manifesto
Individuals and interactions over
processes and tools
Working software over

comprehensive documentation
Customer collaboration over

contract negotiation
Responding to change
over
following a plan
Agile Umbrella
Agile Principles
➢ Customer satisfaction
➢ Changing requirements
➢ Working software
➢ Cooperation
➢ Motivated individuals
➢ Face-to-face conversation
➢ Working software
➢ Sustainable development
➢ Technical and design
➢ Simplicity
➢ Self-organizing teams
➢ Adaptation
A light-weight Agile process Scrum
tool
Split your organization into small, cross-functional,
Self - organizing teams.
Scrum
Product/ Team
Project Owner
Scrum Master
Scrum (contd..)
Split your work into a list of small, concrete
deliverables. Sort the list by priority and estimate the
relative effort of each item.
Scrum (contd..)
Split time into short fixed-length iterations/ sprints
(usually 2 – 4 weeks), with potentially shippable code
demonstrated after each iteration.
January May
Scrum (contd..)
Optimize the release plan and update priorities
in collaboration with the customer, based on
insights gained by inspecting the release after
each iteration.
Optimize the process by having a retrospective
after
each iteration.
Pillars of Scrum
EMPIRICAL PROCESS CONTROL
Pillars of Scrum (Contd…)
1
1 TRANSPARENCY
Visibility to those
responsible for the
outcome.
2
2 INSPECTION
Frequent inspection of
artifacts and progress
towards sprint Goals.
3
3 ADAPTATION
Continuous process of
reviewing and adjusting the
process of materials being
Inspection and Adaption are achieved produced.
through Daily Scrum,
Sprint Review, Sprint Planning15and Sprint Retrospective
TCS-TigoUne Confidential
Values of Scrum
Scrum Framework
Scrum Roles
PRODUCT OWNER
Scrum Roles
DEVELOPMENT TEAM
Scrum Roles
SCRUM MASTER
Scrum Artifacts
PRODUCT BACKLOG & SPRINT BACKLOG
Scrum Artifacts
BURNDOWN CHART
Scrum Events
SPRINT PLANNING
Scrum Events
DAILY SCRUM
Scrum Events
SPRINT REVIEW
Scrum Events
SPRINT RETROSPECTIVE
Agile Metrics
How to use agile metrics to optimize your delivery
The agile metrics discussed below focus on the delivery of software.
Whether you are a scrum or kanban team, each of these agile metrics
will help the team better understand their development process,
making releasing software easier.
Agile Metrics
SPRINT BURNDOWN
● A sprint burndown report then tracks the completion of work
throughout the sprint.
● The x-axis represents time, and the y-axis refers to the amount
of work left to complete, measured in either story points or
hours.
● The goal is to have all the forecasted work completed by the
end of the sprint.
Agile Metrics
EPIC AND RELEASE BURNDOWN
Agile Metrics
VELOCITY
Agile Metrics
CONTROL CHART
Agile Metrics
CUMULATIVE FLOW DIAGRAM
Scrum Metrics
SOFTWARE IS DIFFERENT
● Software development is an intellectual and R&D activity.

● Complexity of the whole system increases much more than linearly with
respect to size.
● Software can be changed easily and with a low cost.
● Large variability.
● Software is invisible.
What is SCRUM
Management framework for iterative incremental product development –

Approach to optimize predictability and control risk
• Scrum provides a structure of roles, meetings, rules, etc. – Scrum doesn't
provide practices
Scrum History
SCRUM is based on the research by Takeuchi and Nonaka – Takeuchi, Nonaka, "The
new new Product Development Game", 1986 – Main ideas:
• No sequential life cycle (i.e., no waterfall)
• No traditional division of labour (self-organizing /multilearning teams)
• Note: SCRUM originally started in hardware (not in software) development
• Formally presented by Sutherland and Schwaber at OOPSLA 1995
Impact of SCRUM
SCRUM has a set of simple rules • These simple rules, however, have very deep
implications in the organization – Change of roles – Change of mindset of •
Management • Developers • Customers – Change of development process
The Agile - Scrum Framework
Scrum with Kanban
Scrum board: You can visualize your sprint backlog with a Scrum task board
. The board can have different forms; it traditionally involves index cards, Post-It notes, or a whiteboard. The
Scrum board is usually divided into three categories: to do, work in progress, and done. The Scrum Team needs
to update the board throughout the entire sprint. For example, if someone comes up with a new task, she would
write a new card and put it in the appropriate column.
A key aspect of Kanban is to reduce the amount of multi-tasking that most teams and knowledge workers are
prone to do and instead encourage them to “Stop Starting! And Start Finishing!”, a mantra coined by Dr. Arne
Roock (of www.Software-Kanban.de). WIP – Work-in-Progress – Limits defined at each stage of the workflow
on a Kanban board encourage team members to finish work at hand and only then, take up the next piece of
work.
Scrum Board Vs KanbanBoard
Xtreme Programming with Scrum
• Popular and somewhat controversial agile method
consisting in values, principles and practices – It can be
used together with SCRUM
• Sit together (Open-Space and communication) •
Whole team (People allocated full time to a project)
• Informative workspace (Blackboard to draw how project
proceeds)
• Energized work – Work only as many hours as you can
be productive – When you're sick, rest and get well –
AGILE TESTING
Eliminating Wastes-Lean Approach in Scrum
1. Overproduction of features and inventory 2. Delays 3. Handoff
(e.g., instead of automatic procedures) 4. Extra-processing and
extra-processes 5. Partially done work 6. Interrupt task
switching 7. Testing and corrections at the end 8. Not using
people's full potential 9. Information scattered (e.g., multiple
documents) Do everything online (e.g., Google docs, wiki) 10.
Wishful thinking (in meeting goals promised
Delivery Vision
We are using scrum with 4 week Sprint and with Sprint review
happening every two weeks
We are using several Agile Methods
Xtreme programming,
Delivery Vision

Agile TRanformation

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Agile TRanformation

Uploaded by

Copyright:

Available Formats

An Overview of

Software development processes

software development 3 TCS-TigoUne Confidential

➔ You complete one phase (e.g. design)

you’re doing right the first

You don’t realize any value until

than Agile approaches 5 TCS-TigoUne Confidential

Not a process, it's a philosophy or set

Working software over

Customer collaboration over

● Software development is an intellectual and R&D activity.

Management framework for iterative incremental product development –

You might also like