1. Agile Methodology
MODULE 3 – Part 2

2. Agile Methodology
Overview:
What is the Agile Methodology?
History
Principles
Characteristics
AGILE Method: SCRUM

3. History
Evolved in the mid 90s as part of a reaction against “heavyweight” methods
e.g. heavily regulated, regimented, micro--managed use of the Waterfall Method
Sought to move away from the Waterfall Method which was seen as bureaucratic, slow, demeaning, and inconsistent with the ways that developers perform effective work
Initially called lightweight methods

4. History
Earlier Methods
Scrum (1986)
Crystal Clear and Other Crystal Methodologies
Extreme Programming (XP) (1996)
Adaptive Software Development (ASD)
Feature Driven Development
Dynamic Systems Development Method (DSDM) (1995)
Agile Modeling
Lean Software Development
Agile Unified Process (AUP)

5. Individuals and interactions over processes and tools
The Agile Manifesto
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer Collaboration over contract negotiation
Responding to change over following a plan

6. The Agile Manifesto
Customer satisfaction by rapid, continuous delivery of useful software
Working software is delivered frequently (weeks rather than months)
Working software is the principal measure of progress
Close, daily cooperation between business people and developers
Face-to-face conversation is the best form of communication

7. The Agile Manifesto
Projects are built around motivated individuals, who should be trusted to get the job done
Continuous attention to technical excellence and good design
Simplicity
Self-organizing teams
Regular adaptation to changing circumstances

8. Agile Characteristics
More adaptive than predictive
Focuses on the near future rather than the distant future
Focuses on adapting quickly to changing realities rather than planning for the entire length of the development process
Has a lot in common with Rapid Application Development

9. Agile Characteristics
Time periods are strict time boxes and are measured in weeks rather than months
Highly collaborative work
Emphasizes real time communication
Emphasizes on building releasable software in short time periods
Customer is on sire and part of the development team

10. Agile Characteristics
Phases
Inception
Elaboration
Construction
Transition

11. Agile Characteristics
Inception Phase
Smallest phase in the project
Ideally short
Goals:
Establish a justification or business case for the project
Establish the project scope and boundary conditions
Outline the Use Cases and key requirements that will drive design tradeoffs

12. Agile Characteristics
Inception Phase (continued)
Goals:
Outline one or more architectures
Identify risks
Prepare a preliminary project schedule and cost estimate
Establish a baseline by which to compare actual and planned expenditures

13. Agile Characteristics
Inception Phase (continued)
Deliverables:
Objectives and Scope of the Project
High Level Use Cases
Candidate Architectures
Project Schedule and Cost Estimates

14. Agile Characteristics
Elaboration Phase
Project starts to take shape
Healthy majority of the system requirements is captured
Analysis of the problem domain
Primary Goals:
Address known risk factors
Establish and validate system architecture
Delve deeper into the requirements previously gathered

15. Agile Characteristics
Elaboration Phase (continued)
Deliverables:
Detailed Use Cases
Conceptual Diagrams
Ex. Process Flow Diagrams, Activity
Diagrams, etc.
Package Diagrams
Architectural Diagrams
Stable System Architecture
Plan for Construction Phase
Including cost and schedule estimates

16. Agile Characteristics
Construction Phase
Largest phase
Where the bulk of the coding takes place
Use cases are translated to demonstrable prototypes
System is built under the foundation laid in Elaboration

17. Agile Characteristics
Construction Phase (continued)
Main Focus: Development of components and features
Implemented in a series of short, timeboxed iterations
Each iteration yields an executable release of software
Deliverables:
First external release of the software
Succeeding releases of the software as per iteration

18. Agile Characteristics
Transition Phase
Product moves from development team to end users
Feedback received may lead to further refinements
Refinements may be incorporated in several iterations

19. Agile Characteristics
Transition Phase (continued)
Activities:
System conversion
Training of end users and maintenance team
Validation of system against end user expectation via beta testing
Quality level validation
Deliverables:
Final release of the system

20. Agile Characteristics
Principles on Code Production
Keep it simple
Have one shared metaphor
Regularly restructure the system (Refactoring)
Continuously integrate and test
Follow coding standards

21. Agile Characteristics
Agile Best Practices
Daily kickoff and review of goals
Short release cycles
Responsive development
Generalism
Use of generic skill sets that are common across the team, instead of reliance on specific skill sets that are scarce

22. Agile Characteristics
Advantages
Customer decides scope, priority, and dates from a business perspective, while technical people estimate and track progress
Incremental development
Emphasis on responsibility for quality
Emphasis on keeping it simple, regular refactoring, and continuous integration and testing

23. Agile Characteristics
Advantages (continued)
Lightweight, efficient, low-risk, flexible, scientific, and fun way of developing software

24. Agile Characteristics
Criticism / Disadvantages
Puts strong dependence on trust
Code-centered rather than design-centered
Lack of orderly design process and structured reviews may lead to extensive and time consuming tests
Lack of structure and necessary documentation

25. Agile Characteristics
Criticism / Disadvantages (continued)
Only works with senior-level developers
Reliance on verbal communication
Requires too much cultural change to adopt

26. Suitability with Types of Projects
AGILE Homeground
Low criticality
Senior developers
Requirements change frequently
Culture that thrives on “chaos” or changing realities

27. Suitability with Types of Projects
PLAN-DRIVEN Homeground
High criticality
Junior developers
Requirements don’t change too often
Large number of developers
Culture that demands order

28. Suitability with Types of Projects
Scrum
Extreme Programming (XP)
Agile Modeling
Agile Unified Process (AUP)
Agile Data Method
Test Driven Development (TDD)
Feature Driven Development (FDD)
Behavior Driven Development (BDD)
Essential Unified Process (EssUP)

29. SCRUM
Originally a rugby term which is short for “scrummage”

30. Suitability with Types of Projects
Characteristics
An iterative incremental process commonly used with the Agile Methodology
Can be used:
For managing software development projects
As a program management approach (Scrum of Scrums)
Works hand in hand with the PSA Time and Material Model

31. Suitability with Types of Projects
Characteristics (continued)
A process skeleton that includes a set of practices and pre-defined roles
Employs “Sprints” – a time period, usually days in which development occurs on a set backlog items that the team has committed to

32. Scrum Roles
Pig Roles – The ones committed to the project and the Scrum process (Scrum Team)
Chicken Roles – The ones not part of the actual Scrum process but are only involved.

33. Pig Roles
Products Owner
The voice of the customer
Responsible for maintaining the Product Backlog
Scrum Master (or Facilitator)
Responsible for the Scrum process
Ensures that Scrum is used correctly and its benefits are maximized.

34. Pig Roles
Team
A cross-functional group of people
Responsible for managing itself to develop the product

35. Chicken Roles
Users
Who the software is built for
Stakeholders
People who have interest in the project
People within or outside an organization that may influence the project’s objectives and outcomes
Managers
The people who will set up the environment for development

36. SCRUM Documents
Product Backlog
The WHAT that will be built
High level document for the entire project
Prioritized list of high level requirements
Contains broad descriptions of all required features, wish list items, etc.
Contains rough estimates

37. SCRUM Documents

38. SCRUM Documents
Sprint Backlog
Tells HOW requirements are to be implemented in the upcoming Sprint
Greatly detailed document enumerating tasks to be completed during the Sprint
Broken down list of tasks, with each task being no more than 16 hours
Tasks are never assigned, but signed-up for by team members

39. SCRUM Documents

40. SCRUM Documents

41. SCRUM Documents
Burn Down Chart
Publicly displayed chart
Shows the amount of remaining tasks for the current Sprint
Updated daily
Gives a simple view of the daily progress of the team during a Sprint

42. SCRUM Documents

43. SCRUM General Practices
Customers are part of the development team
Frequent intermediate deliveries with working functionality
Frequent risk and mitigation plans
Transparency in planning and module development
Frequent stakeholder meetings to monitor progress

44. SCRUM Documents

45. QUESTIONS AND COMMENTS?