INTLAND

SOFTWARE

Agile Software Development Guide

Agile Software
Development

Agile software development is a group of software development

methodologies based on iterative and incremental development,
where requirements and solutions evolve through collaboration
between self-organizing, cross-functional teams.
There are multiple concrete Agile methods. In common, they promote
development, teamwork, collaboration, and process adaptability. The two most
widely used methods are Scrum and Kanban.

Kanban

Scrum

Kanban method can be applied

to the software development
process. Applying the Kanban
methodology helps developers
to visualize the workflow, track
issues and status changes
along the defined and agreed
workflow.

Scrum is an iterative and

incremental Agile software
development framework for
managing software projects
and product or application
development. It defines a
flexible, holistic product
development strategy where a
development team works as a
unit to reach a common goal.

CHAPTER 1

Agile Software Development

AGILE:
More than Just a Software
Development Methodology
To be Agile in business is
to be able to react to the
unexpected, to be able
to adapt to a changing
market environment and
respond to consumers
needs quickly. This
also applies to software
development.

Agile processes address this

At its heart ALM Software

lack of flexibility, enabling

is a Collaboration tool,

developers to manage

designed for efficient working

changing requirements. With

processes, tailored for

Agile, developers can produce

individual business needs. An

and release features and then

innovative ALM solution can

continue to add additional

be also used in non software

features thereafter. There are

development implementations

many development methods

such as in marketing. It is

such as Waterfall, Scrum or XP

built to accommodate SAFe

The Agile software

and these methodologies are

requirements and is therefore

development processes used

still all in use today, however

fully scalable for enterprise

today address not only the

they are increasingly being

use and it is perfect for

needs of developers and

fused together with Agile

geographically dispersed

development but also can be

processes, creating hybrid

users.

used to address the wider

methodologies, solutions

requirements of business.

tailored to individual business

requirements.

Agile development is built upon

development methods of the

An effective software solution

past. Methods that were, and

for managing software

still are inflexible because the

development processes

software development lifecycle

is therefore, one that can

(SDLC) uses defined phases

accommodate different models

of development in which the

of development and even

phases require that one phase

hybrid development methods.

of development must be

ALM is not just for Software

completed before the next is

Development but it is also

begun.

suitable for many areas of

business where change is a
certainty.

CHAPTER 1

Agile Software Development

Is Agile better fit for

fast growing, small
development companies
or is it for software giants?

This article
was inspired
by reading
Eric Ries:
The Lean
Startup.

The answer is of course both,

while encouraging lean thinking.

but implementation happens

It makes the team environment

differently.

a happier place by facilitating a

transparent, cooperative attitude at

In the case of Spotify it seems that

work.

successful implementation of Agile

lead to quick and manageable

In Spotifys case the key elements

growth. Scrum is mentioned as

of Agile success are highly educated

the key for success in competition

management in Agile practice,

with technology giants like Apple,

where teams are led by masters

Amazon, and Google who were

of Scrum. Furthermore, Spotify

all using Scrum, but on a far

kept teams small, working in small

greater scale, with 15,000 or more

clusters of development teams,

programmers.

with each team dedicated to a

piece of the development work.

Dr. Jeff Sutherland, the co-creator

This ensures easier change, and

of Scrum analyzed the main factors

upgrade constantly without breaking

of Spotifys agile success. For

anything else. In addition, their focus

start-ups and small companies

is on constant problem solving,

with 50 - 100 programmers Scrum

removal of roadblocks. When a

is fundamentally a better fit than

business is growing, roadblocks

any other development method.

will arise that can slow down the

This is the key to competing with

speed and sometimes risk the

new industry standards in software

quality of software development. The

development said Dr. Sutherland.

correct attitude is to deal with those

issues by constantly monitoring

Scrum enables quick delivery of

potential obstacles, and removing

results, with focus on customer

them before they become a bigger

values, and sets collaboration and

problem.

communication as top priorities

CHAPTER 1

Agile Software Development

Agile Project Management Tools can be invaluable support for teams working with Scrum.
codeBeamer supports SCRUM based development with Kanban board agile planning board and
sprint-release planning. In Javaforge small and start-up companies can try and use it for free for
Open Source Projects. For enterprise use codeBeamer is available with special pricing conditions
for start ups with small teams (up to 10 users). Intland Software is committed to assisting start ups
and small enterprises to reach their Agile potential!

Agile ALM: Slash Administration for

Software Developers
Software development has always been difficult and risky for business; however
the ability to manage risk and avoid potential failures before they arise is greater
than ever before.
When working with Waterfall, teams collect

ALM manages software development life

product requirements before the development

cycle, Agile enables companies to focus on

process begins and as a result they often

improving the development process.

cant adapt to changed requirements as

quickly as they should. The result is that

ALM tools can no longer be seen as optional

the final product often does not meet

but rather as necessary tools to increase

expectations. This is one reason why

productivity and reduce expense. ALM tools

Waterfall is increasingly being replaced by

are developed to manage software from

Agile development.
Agile software
development enables
teams to re-evaluate
products at any time in the

Learn more about how

codeBeamer ALM software
solution supports different
software development
methodologies

development process and

multiple different vendors

across the enterprise in one
single platform that reduces
operational expenses and
overwhelming administration.
The right ALM tool simplifies
business compliance

turn the development in different directions

of industry regulations by providing

to adapt to changes more quickly to meet

transparency and traceablity.

requirements.
Benefits of Agile ALM in a nutshell:
Agile adoption is accelerating, however it

+20-50% more productivity

requires ALM vendors to integrate Agile

+10% more engagement and

methodologies into the ALM tools and this

is how Agile ALM was born. Agile ALM is

better collaboration
+30-50% improved quality and

a great solution to adapt to changes more

satisfied customers

quickly and release products faster. While

+20-50% faster delivery

CHAPTER 1

Agile Software Development

Track Your Agile Project:

Burndown
Chart
The Agile Manifesto was introduced

Burndown Chart in a nutshell

in 2001 and since then Agile software

development, or lets call it

Burndown chart is one of the most

the Agile Movement

well-know charts. It was developed

has received a lot of

by Ken Schwaber to provide Scrum

attention, growing

community with a tool to plan their

year on year. According

work. Burndown chart is a very

to the 7th Annual State of Agile

effective planning tool if you know

Development Survey, more than

how to interpret the metrics. Lets

84% of the companies surveyed

look into the basics quickly:

had adopted Agile for software

development. One of the

Burndown chart is a graphical

biggest challenges and

representation of work left to

questions for many

complete over time.

organizations is how to

It shows effort /cost spent and

measure the success or

schedule on a daily basis and

failure of an Agile approach.

helps to lower the potential risks

associated with, and required by

There are many ways to measure

Agile performance including:

traditional project management.

It is a great communication tool
empowering customers and

Burndown charts

stakeholders alike, they can follow

Velocity over time charts

project progress on a daily basis.

Current velocity

The remaining task hours

Remaining time and

can be misleading since it can

The overall break down of the

mean different things in different

iteration.

scenarios i.e. 30 hours not

completed or 10 hours completed
and 20 hours not completed work
hours. You should look into the
details to interpret the information
correctly.

CHAPTER 1

Agile Software Development

If you look at the graph you will

a daily basis to have a burndown

see if Sprint commitments were

chart that shows accurate, daily

met and if so, - how smoothly.

status.

You can see if your team

stretched at the end of the Sprint

Burndown chart is the most popular

to meet commitment as well as

tracking tool for organization

if the teams performance was

implementing Agile due to its

consistent or not; with other

effectiveness and simplicity. However,

words you can see if your team is

use it with the aim to enable your

on track or not and reallocate or

team to produce potentially shippable

reprioritize work accordingly.

and working increments.

Burndown Chart:
Scenarios to Consider
While nothing is black and white,
there are scenarios they can
cause your burndown chart to be
misleading:
If it takes longer than 12 hours
to complete a task, it can be
difficult to track. Encourage team
members to create tasks shorter
than 12 hours.
Teams usually update the effort
column on a daily basis but they
need to re-estimate
how much effort
they will need
to complete
the task. If they
dont, effort
remaining and
effort spent graphs wont be
consistent and can be easily
misunderstood. Team members
should understand that they need
to update effort remaining on

codeBeamer ALM (Application

Lifecycle Management) solution
provides your team with 5 key
modules to manage software
development lifecycle as well as
diverse charts to measure Agile
performance.

Agile Software Development

Methodologies

Agile vs. Waterfall

Agile won the game?
The statistics define success, when

The general answer is very simple:

software development projects

No, any methodology by itself is not

are implemented within the given

a recipe for success. Projects can be

timeframe, on-budget and with the

different, in terms of duration, budget,

requested features.

complexity, number of stakeholders.

Does it mean that agile

methods are the universal key
to success? Is Agile better
than Waterfall?

Agile is not a one size fits all

approach. Waterfall projects suits to
some types of projects and Agile to
others, usually smaller, less critical,
more local scope and more oriented
to end-user. Risk of failure is a nature
of software development.

Waterfall
29%
14%

Agile
Successful

9%

57%

Statement:
Agile projects
are successful
three times
more often
than nonagile projects,
according to
the CHAOS
report from
the Standish
Group.

42%

49%

Challenged
Failed

Source: The CHAOS Manifesto, the Standish Group, 1012

CHAPTER 2

Agile Software Development Methodologies

Does it than mean that Agile projects simply manage risk better than Waterfall?
The answer is yes, but it does not mean that failure will be avoided by using Agile methods.
Agile methods provide a good toolset that helps to minimize and manage risk effectively.
Simply because agile requires better collaboration, more communication, end-user involvement,
shorter, more iterative phases with quicker delivery of results. The success mostly depends on
the stakeholders of the project, success is the success of a team, not the project itself. The
successful implementation of Agile software projects also depends on the maturity of the clients
expectations. A major portion of software project failure is due to a client who is unable to define
the scope.

Summary:
Agile is not 100% recipe for success
Risk and failure are both nature of software projects
Methods can be applied according to certain circumstances case by case decision
Requirements management is a critical part of success
Using a comprehensive integrated ALM tool which supports both Waterfall and Agile methods
gives the freedom to apply methods that fits to the project attributes.
Check how codeBeamer supports Agile and Waterfall.

CHAPTER 2

Agile Software Development Methodologies

Project managers often face long development

cycles, constantly changing priorities that

The most important details to know

about Agile-Waterfall Hybrid

disrupt the product development process and

consequently leading to a final product that
does not meet expectations.

Implementing Agile-Waterfall Hybrid allows

software teams to work Agile, while
hardware development teams and product

Agile-Waterfall Hybrid:
Smart Approach or
Terrible Solution?

managers can use traditional PMP/waterfall

approach.
Tight, continuous integration between PMP
and Agile software development processes
from product concept until validation and
production. As with all software development

Traditional project management methodologies

methodologies, collaboration is key and

are often blamed for being unable to adapt to

Agile-Waterfall Hybrid interface enables

the changes which often makes testing products

teams to define requirements and adapt

or changing alterations quite impossible. The

to changing requirements and provide

Agile approach is often considered as the

feedback from both PMP and Agile sides

perfect solution, especially for projects with

allowing for continuous delivery.

multiple changes. Time is usually less critical in

the Agile world while iteration status can be

The hybrid model is best suited for reuse of

constantly checked and adjustments can be

software code where dealing with a series of

made as long as the product is not ready to be

similar products and where future products

released. The Agile approach has many positive

must also be considered. Such situations

points, it is important to note that it is not a

result in lead to a quick turnaround, with

one-fits-all solution and as a result we often

continual product releases. Backlog

see hybrid solutions.

management is critical area for successful

adoption of this hybrid model and adoption

Hybrid models are usually born from the

is best assisted by software version release

compromise between different methods. One

planning features.

of the most popular today is Agile-Waterfall

Hybrid described by Erick Bergmann and Andy

Hamilton. The Agile-Waterfall Hybrid model is
far from perfect and it is a compromise. It has as
many advantages and disadvantages, just as all
methodologies. The Agile-Waterfall hybrid it is
often considered as a smart approach to adapt
both methodologies without compromising too
much.

CHAPTER 2

Agile Software Development Methodologies

As with all hybrid models both sides must

The Agile Waterfall model aims to retain the

compromise, where the Waterfall development

dependency tracking and clarity of Waterfall

must give up some certainty of fixed

whilst embracing the strengths of Agile

expectations, for the flexibility and freedoms

methodology, providing the flexibility and

of the Agile world. The Agile compromise is to

transparency necessary to adapt to the fast

be creative but with far less freedom, working

changing requirements of stakeholders.

against a fixed deadline with cost forecasting

and risk assessments.

Being Agile: Switching from

Scrum to Kanban

When companies go Agile

is to be flexible enough to

into short periods called sprints

for the first time they tend to

manage changing requirements

and include the client within the

adopt Scrum. For enterprise the

and develop better products,-

development process.

key benefit of using Scrum in

faster. Scrum enables teams to

software development projects

package the development work

CHAPTER 2

Agile Software Development Methodologies

it creates a quick turnaround from initial

Quick comparison of
Scrum and Kanban

identification of problems and bugs or

Work commitments required by Scrum, are

Teams benefit from constant feedback and

additional requirements for new features,

to final implementation. It increases the rate

optional in Kanban
In Scrum work items should be broken down

of production whilst reducing the cost of

to be completed within 1 sprint as opposed

production and it produces a better featured

to no size limits in Kanban.

product.

Recommended use of Burndown Charts

in Scrum whereas in Kanban no particular

Scrum or Kanban:
Which One Is Better?
No question about it that Scrum is a great Agile
software development framework, however its
performance can be beaten by Kanban due
to bottlenecks in work flow for testing and
deployment. By using Scrum product owners
can determine the user stories and turn these
into sprints. Small stories often fail to produce a
shippable product by the end of the sprint and
as a result, multiple sprints are required and
this results in increased complexity that can be
difficult to manage. Kanban addresses these
weaknesses of Scrum.

How Does Kanban Improve

Decision Making?
Kanban is all about real-time decision making
and visualization of workflow. As a result Kanban

diagram is prescribed.
Estimation necessary in Scrum whereas in
Kanban estimation is optional.
Many of the requirements of working with Scrum
are optional in Kanban. This is because Scrum
represents an earlier idea of Agile; Kanban
removes many of these working requirements
of Scrum, and instead are offered as optional
extras in Kanban, only to be implemented if the
project requires it. The good news is that there is
no need to switch entirely from one to the other
but rather a partial transition process by process
from Scrum to Kanban is possible as the team
becomes more experienced. Alternatively, just
Keep the best of both Scrum and Kanban as a
permenant fixture if it works for your business, the combination of the two is commonly referred
to as Scrumban.

is suited to specific areas of business that

requires quick decisions, where there is no time
to talk endlessly about the consequences.
For a development team working with Kanban,
every team member is trusted and empowered
to take make quick decisions. Scrum is great
to practice for Agile working and team building,
whereas Kanban greatly improves on Scrum by
assisting developer teams to act more quickly
to avoid delayed decisions and unnecessary
expenses.

Check out
how to practice
Scrum or Kanban
with
codeBeamer
ALM solutions.

CHAPTER 2

Agile Software Development Methodologies

The Main
Benefits
of Using
Scrum
Scrum certified trainer
Kenny Rubin, author of the
best-selling book entitled,
Essential Scrum: A
Practical Guide to the Most
Popular Agile Process,
published his blog post
highlighting the main
benefits of using Scrum
method.

Delivering features today

generates revenue and
feedback today.

collect feedback from clients

The third big area of Scrum

as quick as possible. Therefore

benefits is provided by the

Scrum speeds up bug fixing

strong focus on collaboration

processes and new feature

and daily communication.

development, that makes

Scrum provides visibility on

customers happy.

tasks for each team member, to

track progress and allow better

Applying Scrum in development

allocation of resources. The

can reduce the cost of

strong collaboration focus leads

production. Product cost is

to more happy and productive

determined by time and effort

team.

Kenny highlighted the main

spent on new releases, but

benefits of using Scrum in

companies are rarely able to

Scrum as an agile method

development, which is speeding

estimate real cost of production.

that ensures quicker response

up delivery of new products and

In Scrum story pointing can

to market demand and leads

new features by developing in

be applied to estimate tasks

to cost savings via increased

short sprints. Kenny defined

complexity. Complexity strongly

performance of teams.

3 main areas of benefits. The

relates to cost of production.

According to my experience

first and most important is

Story pointing on each tasks

Scrum can be used not only in

getting delighted customers,

gives the opportunity to better

software development, but in

which means, in Scrum sprints

estimate the cost of developing

sales and marketing as well.

are really short, so results

new features, and also allows

are delivered and ready for

project managers to prioritize

test within 1-3 weeks. The

tasks according to their

Scrum methods main focus

complexity.

is to provide new features or

corrections frequently, and

Read more about

Scrum

CHAPTER 2

Agile Software Development Methodologies

Why use Kanban in

software development?
Kanban, as a method has its roots in production and is an important element of both
Kaizen and Lean production. Kanban is focused on pull strategy, with resources
allocated based on where and when they are needed to support just in time delivery.
But how can Kanban be applied in software development and what are the benefits of
using this method?
The principle method of

easier decision-making on

issues, problems, risks

visualization in Kanban is

changes.

among team mates. Using

the Kanban board and in a

production environment, this is

this method it facilitates

Shows WIPs

the consensus around

a physical board where tickets

The critical element is that

for the demand of resources are

work-in-process at each

placed. In software development

state in the workflow is

it is impossible to use physical

limited and that new work

and experimentation

boards, where teams are

is pulled into the new

Kanban encourages small

working in virtual environment

information discovery

continuous, incremental and

mostly in distributed locations.

activity when there is

evolutionary changes that

In software development a

available capacity within the

stick. For example Kanban

virtual Kanban board can be

local WIP limit.

can support effectively the

applied. Kanban is a method

that greatly assists teams to be

improvement suggestions.
Forces collaboration

daily stand up meeting of

Helps to manage the flow

Scrum, as it gives a quickest

Agile and therefore agile project

The flow of work through

overview on tasks, status,

management and ALM tools

each state in the workflow

WIPs for a better resource

usually provide a Kanban board

should be monitored,

allocation and increases

(electronic cardboard) view.

measured and reported.

the motivation and self-

Kanban board is also helpful

governance of teams.

How Kanban delivers

benefits in software
development:
Easier changes
Cardboard column names
represent the different states
of workflow. Visualizing
the flow of work is core to
understanding how work
proceeds, and ensures

for project managers to get

insight into the progress of
work.
Supports problem solving
and risk management
Due to the explicit
understanding of how things
work and how work is
actually done, it is possible
to move to a more rational,
objective discussion of

CHAPTER 2

Agile Software Development Methodologies

Scaled Agile
Framework
(SAFe) in a
nutshell
In the beginning agile development was used
for pilot projects at enterprise level, developers

Quick insight into Scaled Agile

Framework (SAFe)

worked in small teams experimenting with

working lean and agile methods. The pioneers

Scaled Agile Framework (SAFe) is one of the

noted what worked and what didnt, and

most implemented scaled agile frameworks of

developed various frameworks and strategies for

the time. Lets have a quick insight into SAFe:

scaled agile adoption.

What is Agile and Scrum for teams, that
Agile adoption by enterprises has boomed in the

is SAFe (Scaled Agile Framework) for

last few years. As more enterprises realized its

companies

benefits, more executives started to pay more

attention to implement and practice lean and
agile methods. The most important management
responsibility is still to measure improvement
and ROI. One vital role of management, is to

Scaled Agile Framework (SAFe) is created by

Dean Leffingwell
Describes three levels of scale including
team, program and portfolio level
Describes the working progress between

select the software solution that best fits to their

team level development and business

business model, products and assists to shorten

strategy

the delivery and release phases in order to

Provides PSI and Release Planning

outperform competitors.

Constantly evolving, free IP framework

More information and success stories are on

Once enterprises decide to go agile they

the SAFe homepage.

can choose from different methodologies and

frameworks. However experts and consultants
tend to specialize in one and promote it
exclusively, there is no universal agreement
about which is the best framework or method.
There is no one-size-fits-all solution and every
framework has pros and cons.

Learn more about Scaled

Agile Framework (SAFe)

Agile Adoption

gile is used widely by software developers

Development), Adaptive Software Development,

and Scrum teams for more than a decade.

RUP (Rational Unified Process) or the more

Now Agile which is in an alternative to Waterfall

recent Scaled Agile Framework (SAFe)

seems to be the new standard for enterprises.

according their needs.

Today more and more enterprises are realizing

the benefits of Agile and the implementation

As Ken Schwaber stated SAFe is built on

of Agile is ramping up; especially in the

different iterative and incremental predecessors

industries where it is important to shorten the

such as Rational Unified Process (RUP), the

delivery and release

popular iterative

phases. The real

and incremental

challenge is how

software

to adopt teams
practices where
every team member
is responsible

Learn more about our codeBeamer

(commercial version) or try out
the free open source version of
codeBeamer at JavaForge.com.

development
process framework.
The key question is
if enterprises really

for implementing

benefit from Scaled

and executing

Agile Framework

certain tasks at the

(SAFe) developed

enterprises level.

by Dean Leffingwell and which is all about using

the Agile framework at the Enterprise level. The

If enterprises decide to Go Agile they can

Agile Enterprise Adoption with the Scaled Agile

choose from different methodologies and

Framework is accelerating, and speaking from

processes such as Scrum, XP (eXtreme

our own experience, we have seen remarkable

Programming), Crystal, FDD (Feature Driven

results achieved by adopting SAFe at Enterprise

Development), DSDM (Dynamic Systems

Level.

Agile Adoption
by Enterprises is

Ramping Up

CHAPTER 3

Agile Adoption

We started to develop codeBeamer over

management tools. Another key differentiator

a decade ago now and it still remains the

is that codeBeamer provides Versioning

most innovative product on the market

(baselines) for all artifacts for compliancy, so

place. With the new release of codeBeamer

vital for quality assurance (QA) management

7.2 it has become the most comprehensive

and traceability.

implementation of SAFe in the Agile world.

Besides SAFe codeBeamer ALM solution also

It sets itself apart from its competitors in

supports software development methodologies

that it enables Agile planning / scheduling

such as Agile, Waterfall and Agile-Waterfall

while maintaining an established discipline

hybrid.

of requirements, tests and development

Download

codeBeamer 7.3

or contact our Sales Department at [email protected] to request a demo.