AGILE PERSPECTIVE

This document is created to provide a quick overview of frameworks, approaches, techniques, and
methodologies (as applicable).

The information is gathered from BABOK v3 and other reference websites.

Version 1.0
AGILE APPROACHES
APPROACHES DESCRIPTION
Crystal Clear Crystal Clear is a member of the Crystal family of methodologies. It is
considered an example of an agile. Crystal Clear can be applied to
teams of up to six or eight co-located developers working on systems
that are not life - critical. E.g., Crystal Yellow, Crystal Orange and
others, whose unique characteristics are driven by several factors
such as team size, system criticality and project priorities.
DAD (Disciplined Agile Disciplined agile delivery (DAD) is the software development portion
Delivery) of the disciplined agile toolkit. DAD enables teams to make simplified
process decisions around incremental and iterative solution delivery.
DAD builds on the many practices espoused by advocates of agile
software development, including scrum, agile modelling, lean
software development, and others.
Dynamic Systems It is a generic approach to project management and solution delivery
Development rather than being focused specifically on software development and
Method (DSDM) code creation and could be used for non-IT projects.
Evolutionary Project The other agile methodologies fall short when it comes to focus
Management on delivering measurable multiple value requirements to
(Evo) stakeholders. In Evo, the main idea is that every step of the project
delivered tangible value to stakeholders.
Extreme Programming Similar to SCRUM but few differences like:
(XP) • The sprint can be shorter like 1 or 2 weeks long
• Changes accepted during the sprint.
• Priority of the feature development set by customer (rather
by the Product Owner) and is strictly followed.
Follows engineering practices like TDD, Pair Programming etc.
Feature Driven Feature-Driven Development (FDD) is a client-centric, architecture-
Development centric, and pragmatic software process. As the name
(FDD) implies, features are an important aspect of FDD. A feature is a small,
client-valued function expressed in the form. Features are similar to
use cases. Steps involved are:

• Develop an overall model

 • Build a Features List
• Plan by Feature
• Design by Feature
• Build by Feature
Kanban Kanban is a workflow management method for defining, managing,
and improving services that deliver knowledge work. It aims to help
you visualize your work, maximize efficiency, and improve
continuously.
It gives a clear visual of the state of all the items. It limits the WIP of
number of items for the team and controls the workflow.
Scaled Agile Framework It is used to implement agile practices at enterprise scale.
(SAFe™) The framework is a body of knowledge that includes structured
guidance on roles and responsibilities, how to plan and manage the
work, and values to uphold.
Scrum A lightweight process management framework based on
empirical process control. Work is performed in a series of
fixed length iterations, called Sprints, which last one month
or less. At the end of each sprint the team must produce
working software of a high enough quality that it could
potentially be shipped or otherwise delivered to a customer.
Techniques used within Agile Approaches:

TECHNIQUES DESCRIPTION
Behaviour Driven Behaviour-driven development (BDD) is an Agile software
Development (BDD) development methodology in which an application is documented
and designed around the behaviour a user expects to experience
when interacting with it.
Kano Analysis The Kano Model is one of many prioritization frameworks designed to
help product teams prioritize initiatives. Kano can help teams
determine which features will satisfy and even delight customers.
Product managers often use the Kano Model to prioritize potential
new features by grouping them into categories.
Lightweight It is a principle that governs all documentation produced on
Documentation an agile project. Agile recommends less documentation with just
enough information. JIT is a good approach for documentation.
MoSCoW Prioritization A method to prioritize requirements (stories or other elements)
MoSCoW (must have, should have, could have, won’t have) provides
a way to reach a common understanding on relative importance of
delivering a story or other piece of value in the product.
The prioritization on product backlog uses this method.
Personas Fictional characters or archetypes that exemplify the way
that typical users interact with a product.
The Personas can be used to help clear the requirement in the user
stories. The development team empathise with the created personas
for a focused solution.
Planning Workshop A collaborative workshop that is used to allow an agile
team to determine what value can be delivered over a time
period such as a release. For example, sprint planning where the
team collaborated and plan for the next upcoming sprint of what
needs to be delivered to the stakeholder.
Purpose Alignment It is a model that is used to assess ideas in the context of
Model customer and value.
 It rates features, processes, products, or capabilities in two
dimensions. Business analysis practitioners use this information to
help recommend the best actions to improve them based on the
ratings.
Real Options An approach to help people know when to make decisions
rather than how.
Real Options has three simple rules:
• options have value,
• options expire, and
• never commit early unless you know why.

For Example.
A user story: an option to implement a piece of functionality. The
option expires when the business need changes.

Relative estimation Relative Estimation is used to make future predictions based on past
experience, knowledge, complexity, size, and uncertainty required to
complete backlog items.
The size is measured in story points and uses Fibonacci scale.
For example, Planning Poker, Silent Sizing etc.
Retrospectives It is a Lesson Learned technique.
Retrospectives focus on continuous improvement of the
teamwork process and are held after every iteration on agile projects.
After the iteration is over the internal team focuses on improvement.
It answers two questions
1. what went well
2. what can be improved
Story Decomposition This technique ensures that the requirements for a product are
represented at the appropriate level of detail and are derived from a
valuable business objective.
The bigger stories (requirements) are broken down into granular
stories aligned with desired outcomes.
Story Mapping Provides a visual and physical view of the sequence of
activities to be supported by a solution.
 The visual representation uses the user stories to depict the activities.
It helps in understanding of product functionality, the flow of usage,
and to assist with prioritizing product delivery.
Storyboarding Storyboarding is used to describe a task, scenario, or story in terms of
how stakeholders’ interactions with the solution. Storyboarding is
used in conjunction with other techniques such as use cases, user
stories, and prototyping to detail visually and textually the sequence
of activities summing up different user interactions with the solution.
Value Stream Mapping Provides a complete, fact-based, time-series representation
of the stream of activities required to deliver a product or
service to the customer.
This technique helps in identifying the areas in the process which
leads to waste time.