Tools and Links

AGILE - Training AGILE- Frameworks AGILE - Links

Agile Frameworks

Agile is a framework that is based on the Agile Manifesto for Software Development. It is a mindset that focuses on nurturing innovation with iterative and incremental production. Product of chucks of value are presented frequently to obtain feedback for continuous improvement. There are numerous framework options that can be used for a particular project. Listed below are the details for each framework and links to obtain additional information.


Team Size/
Iteration Lengths

Pros. Cons.
An iterative and incremental software development framework for managing software projects.
•  Small
•  (5-9 members)

• 30 day maximum
• (2 to 3 weeks preferred)
•   Breaks projects into manageable chunks
•   Adaptable to change in scope and requirements
•   Must have dedicated stakeholder involvement to be successful
•   Needs experienced team members
•   Team members must be committed
Extreme Programming (XP)
Intended to improve software quality and responsiveness to changing customer requirements.
•   Small (2-10 members)


•   2-week iterations, not to exceed 3 weeks
•   Values Communication
•   Focuses on design
•   Establish rational plans and schedules to get the developers committed to their schedules
•   Lack design documentation
•   Highly prescriptive
•   Does not address deployment
Kanban, meaning “visual sign” or “card” in Japanese, is a visual framework to implement Agile. It promotes small, continuous changes to your current system.
•   N/A

•   ​1 week iterations
 •   Allows teams to visualize work and eliminate bottlenecks
•   ​Limited visibility in dependent tasks
•   Difficult to obtain status
Lean Software Development (LSD)
Takes Lean manufacturing and Lean IT Principles and applies them to software development
•   ​N/A
•   Seeks to improve organizations from the top down approach
•   Guidelines for business enterprise defined
•   Limited change in requirements
•   Limited documentation for applying in software environment
​Scaled Agile (SAFe)
A method to assist large businesses adopt Agile. SAFe is based on Lean and Agile principles and tackles tough issues in big organizations, like architecture, integration, funding, and roles at scale
•   Multiple teams

•   ​3-5 iterations
•   Ability to manage multiple scrum teams across the enterprise
•   Involves all levels in your organization
•   Focuses team attention on upcoming release
•   Lack of maturity and field testing
•  Numerous methods combined into one framework
•   Highly prescriptive
Feature Driven Development (FDD)
An iterative software development methodology intended for use by large teams working on a project using object-oriented technology.
•   Small to Large (4-20 depending on complexity)

•   2-week iterations recommended
 •  Helps to move larger sized projects and obtain repeatable success
•   Provides detailed guidelines for multi-team projects
•   Only addresses design and implementation
•   Requires highly experienced experts for modelling
•   Not an ideal methodology for smaller projects
Adaptive Software Development (ASD)
Represents the idea that projects should always be in a state of continuous adaptation.
•   Small to Large (depends on scope)

•   4-week iterations for small projects and 8-week for medium/ large
 •  Very strong in non-technical aspects of software development
•   Does not provide guidelines for individual development projects
•   Weak on Metrics
•   Does not address technical aspects
Dynamic Systems Development Method (DSDM)
Used for developing software and non-IT solutions. It addresses the common failures of IT projects, like going over budget, missing deadlines, and lack of user involvement.
•   Small (2-10 members)

•   N/A
•   Highly dependable
•   Provides well-defined guidelines for the business system, concept development, and requirements.
•   Details and white papers available only to DSDM Consortium members
•   Costly to implement
•   Relatively New Model
Crystal Clear
This is part of the Crystal family of methodologies. It can be used with teams of six to eight developers and it focuses on the people, not processes or artifacts.
•   Supports Any Team

•   Up to 4 month iterations
•  Strong of communication
•   Well-defined for project teams and technical practices
•   Removal of bureaucracy or distractions
•   High user involvement, adaptability
•   Not prescriptive
•   Need to be experienced in Software Development to utilize
Test Driven Development (TDD)
Relies on repetitive, short development cycles. A developer writes an (initially failing) automated test case for a new feature and quickly adds a test with the minimum amount of code to pass that test.
•   Supports Any Team

•   N/A
•   Enables you to develop small chucks of code when writing software
•   Low adoption rate
Rapid Application Development (RAD)
This is an effective methodology to provide much quicker development and higher-quality results than those achieved with the other software development methodologies

•   N/A

•   Helps to reduce the risk and required efforts on the part of the software developer
•   Encourages customer feedback which provides improvement scope for any software development project
•   Better Quality
•   Depends on the strong team and individual performances for clearly identifying the exact requirement of the business
•   Only works systems that can be modularized
•   Demands highly skilled developers and designer’s team which may not be possible for every organization
Large-Scale Scrum (LeSS)
A product development organizational framework that extends Scrum with scaling rules and guidelines without losing the original purposes of Scrum.
•  Framework 1: Up to 10 teams
•  Framework 2: more than 10 teams 

•   N/A
•   Considered to be the “most” Agile scaling method
•   The least prescriptive method which leaves some gaps for organizations to fill
A framework that drives to the heart of scaling by minimizing cross-team dependencies and integration issues. An exoskeleton that rests on top of multiple Scrum Teams when they are combined to create an Integrated Increment
•   Multiple Teams (3 to 9)

•   30 day maximum
•   (2 to 3 weeks preferred)
•   More attention is paid to dependencies and interoperation between Scrum Teams, delivering one “Done” Integrated Increment at least every Sprint
•   Consist with Scrum Framework
•   Does not cover other organizational considerations like Org Structure
•   Light on details
Agile Modeling
A collection of values, principles, and practices for modeling software that can be applied on a software development project in an effective and light-weight manner. It is a supplement to other agile development methodologies such as Scrum, extreme programming (XP), and Rational Unified Process (RUP)
•   ​N/A
•   Open and honest communication
•   Feedback
•   Focused on quality work
•   Significant dependence on personal communication and customer collaboration
•   Can be difficult to apply
Disciplined Agile Delivery (DA 2.0)
A process decision framework for lean enterprises. The main characteristics of this framework are that it: is a people-first, learning-oriented hybrid agile/lean approach; has a risk-value delivery lifecycle; is goal driven; is enterprise aware; is tactically scalable at the team level; and strategically scalable across all of the enterprise.
•   Small to large teams (2 members to 100)

•   N/A
•   There is no single strategy (such as Agile/Scrum, Lean, and SAFe that applies to all situations.
•   Provides a foundation from whcih to scale agile software delivery
•   It's in the early stages, so it is not as well-known as other frameworks
•   ​Makes the complexities of solution delivery clear, which can overwhelm anyone looking for a simple, "just tell me what to do" strategy.

back to top