A Simple Self-made handbook to simplify Agile

1. WHY AGILE?
15th November, 2016
Author – Deepraj Pathak

2. DEFINITION
• Able to move quickly and easily
• Relating to or denoting a method of project management, used especially for
software development, that is characterized by the division of tasks into short
phases of work and frequent reassessment and adaptation of plans.
• Agile methods replace high-level design with frequent redesign

3. WHAT IS SDLC?
What is the system development?
• Systems development is the process of defining, designing, testing, and implementing a new
software application or program. It could include the internal development of
customized systems, the creation of database systems, or the acquisition of third
party developed software.
• SDLC(System Development Life Cycle) is a term used in systems engineering, information
systems and software engineering to describe a process for planning, creating, testing, and
deploying an information system.
What is SDLC in project management?
• The systems development life cycle (SDLC) is a conceptual model used in project
management that describes the stages involved in an information system
development project, from an initial feasibility study through maintenance of the completed
application.

4. SDLC UNLEASHED
Stage 1: Planning and Requirement Analysis
Stage 2: Defining Requirements
Stage 3: Designing the product architecture
Stage 4: Building or Developing the Product
Stage 5: Testing the Product
Stage 6: Deployment in the Market and Maintenance

5. POPULAR SDLC MODELS
Following are the most important and popular SDLC models followed in the
industry:
• Waterfall Model
• Iterative Model
• Spiral Model
• V-Model
• Big Bang Model
• Amongst all the above mentioned models, WATERFALL model got huge popularity
worldwide.

6. WATERFALL CHALLENGES
Waterfall challenges
• Traditional Waterfall treats analysis, design, coding, and testing as discrete phases in a
software project. This worked OK when the cost of change was high. But now that it's low it
hurts us in a couple of ways.
1. Poor quality
First off, when the project starts to run out of time and money, testing is the only phase left.
This means good projects are forced to cut testing short and quality suffers.

7. 2. Poor visibility
Secondly, because working software isn't produced until the end of the
project, you never really know where you are on a Waterfall project. That
last 20% of the project always seems to take 80% of the time.
WATERFALL CHALLENGES

8. 3. Too risky
 Thirdly you've got schedule risk because you never know if you are going to make it until
the end.
 You've got technical risk because you don't actually get to test your design or architecture
until late in the project.
 And you've got product risk because don't even know if you are building the right until it's too
late to make any changes.
WATERFALL CHALLENGES

9. 4. Can't handle change
And finally, most importantly, it's just not a great way for handling change.
WATERFALL CHALLENGES

10. THE AGILE APPROACH
Instead of treating these fixed stages Agilists believe these are continuous activities.By doing them
continuously:
• Quality improves because testing starts from day one.
• Visibility improves because you are 1/2 way through the project when you have built 1/2 the features.
• Risk is reduced because you are getting feedback early, and
• Customers are happy because they can make changes without paying exorbitant costs.

11. KEY PRINCIPLES OF AGILE
There are 10 key principles of agile. These are characteristics that are common to all agile
methods, and the things that I think make agile fundamentally different to a more traditional
waterfall approach to software development. They are:
1. Active user involvement is imperative
2. The team must be empowered to make decisions
3. Requirements evolve but the timescale is fixed
4. Capture requirements at a high level; lightweight & visual
5. Develop small, incremental releases and iterate
6. Focus on frequent delivery of products
7. Complete each feature before moving on to the next
8. Apply the 80/20 rule
9. Testing is integrated throughout the project lifecycle – test early and often
10. A collaborative & cooperative approach between all stakeholders is essential

12. DIFFERENT AGILE IMPLEMENTATIONS
XP Implementation Adaptive Software
Development
Implementation
SCRUM Implementation

13. I AM LISTENING……….
QUESTIONS?

14. THANK YOU 