You are on page 1of 2

Agile software development has been gaining momentum over the years as more and

more people start to see problems with the traditional model, and the benefits a
gile methodologies bring. In agile, development happens in iterative cycles and
improvements are made in each iteration. Feedback is gathered as early as possib
le, improving customer engagement and team collaboration. All of these actions h
elp development teams to better anticipate and manage changes.
Atlassian, the maker of popular issue tracking software JIRA, recognizes the val
ues agile can bring. It has become a leader in agile software development by com
ing out with JIRA Agile, a product that adds agile support to JIRA. In this chap
ter, we will introduce the basics of JIRA Agile.
By the end of the chapter, you will have learned:
What JIRA Agile is
The different options to install JIRA Agile
The key concepts and terminologies
Creating new agile projects with project templates
As you can see, installing JIRA Agile is simple and straightforward. However, th
ere
might be times when you cannot use the Universal Plugin Manager (UPM). In these
cases, you will need to manually download JIRA Agile from https://marketplace.
atlassian.com/plugins/com.pyxis.greenhopper.jira onto your local computer
first, then upload and install it via the UPM.
You might want to do a manual installation if you need to install a specific ver
sion of
JIRA Agile due to version compatibility issues or other bugs with the latest rel
ease.
Another reason would be if your JIRA does not have access to Atlassian Marketpla
ce
due to network or firewall settings. To manually install JIRA Agile:
1. Go to the preceding link and click on the Download link to get the add-on
file.
2. Go back to JIRA and click on the cog icon in the top right-hand corner and
select the Add-ons option.
3. Select the Manage add-ons option from the left-hand panel.
4. Click on the Upload add-on link:

Unlike the traditional waterfall methodology where every task or project phase i
s
sequential, Scrum prescribes the notion of iteration. At a high level, with Scru
m, a
project is broken up into a number of iterations called sprints. Each sprint is
usually
one or two weeks long; the project team completes a portion of the overall proje
ct,
and the project is completed when all the sprints are finished. With this approa
ch,
the project team is able to do the following:
Continuously deliver with each sprint, so feedback can be gathered early
Accommodate changes during the project life cycle
The distinction between fast and slow thinking has been explored by
many psychologists over the last twenty-five years. For reasons that I
explain more fully in the next chapter, I describe mental life by the metaphor

of two agents, called System 1 and System 2, which respectively produce


fast and slow thinking. I speak of the features of intuitive and deliberate
thought as if they were traits and dispositions of two characters in your
mind. In the picture that emerges from recent research, the intuitive System
1 is more influential than your experience tells you, and it is the secret
author of many of the choices and judgments you make. Most of this book
is about the workings of System 1 and the mutual influences between it
and System 2.

You might also like