Notesale: Turn your study into money

Document Preview

Extracts from the notes are below, to see the PDF you'll receive please use the links above

---

AGILE METHODOLOGY
Agile software development is a group of software development methods based on iterative
and incremental development, where requirements and solutions evolve through
collaboration between self-organizing, cross-functional teams
...
It is a conceptual framework that promotes foreseen
tight interactions throughout the development cycle
...
Since then, the Agile Movement, with all its
values, principles, methods, practices, tools, champions and practitioners, philosophies and
cultures, has significantly changed the landscape of the modern software engineering and
commercial software development in the Internet era
...
Agile
approaches are typically used in software development to help businesses respond to
unpredictability
...

Because of this popularity, many organizations claim to be “doing Scrum” but aren’t doing
anything close to Scrum’s actual definition
...
Doing Scrum as it’s actually defined usually comes into conflict with existing
habits at established non-Agile organizations
...
These are described
in detail by the Scrum Training Series
...
Scrum has five meetings: Backlog
Grooming (aka Backlog Refinement),Sprint Planning, Daily Scrum (aka 15-minute standup),
the Sprint Review Meeting, and the Sprint Retrospective Meeting
...
Ken Schwaber,
Mike Beedle, Jeff Sutherland and others have contributed significantly to the evolution of
Scrum over the last decade
...

In Scrum, the "Product Owner" works closely with the team to identify and prioritize
system functionality in form of a "Product Backlog"
...
- whatever needs to be done in order to
successfully deliver a working software system
...
Once a Sprint's
Product Backlog is committed, no additional functionality can be added to the Sprint except
by the team
...

Scrum has been proven to scale to multiple teams across very large organizations with 800+
people
...

WHERE DID AGILE COME FROM?
In 1970, Dr
...
He asserted that software
should not be developed like an automobile on an assembly line, in which each piece is added
in sequential phases
...
Dr
...
Royce specifically objected to
this approach due to the lack of communication between the specialized groups that complete
each phase of work
...
First of all, it assumes that every requirement of the project can be identified
before any design or coding occurs
...
In that scenario, a company has spent time and money to create software that no
one wants
...
This is achieved through regular cadences of work,
known as sprints or iterations, at the end of which teams must present a potentially
shippable product increment
...
” In waterfall, development teams only have one chance to get each aspect of a
project right
...

— is continually revisited throughout the lifecycle
...

The results of this “inspect-and-adapt” approach to development greatly reduce both
development costs and time to market
...
And because a team’s work cycle is limited to two
weeks, it gives stakeholders recurring opportunities to calibrate releases for success in the real
world
...
Instead of
committing to market a piece of software that hasn’t even been written yet, agile empowers
teams to continuously replan their release to optimize its value throughout development,
allowing them to be as competitive as possible in the marketplace
...

Agile Methodology is an incremental, repetitious means of managing projects; particularly in the
field of software development
...

An idea conceived in the early 90's, Agile Methodology was built upon the foundations of the
traditional waterfall sequential methods of the 1970's
...
His theory was that software systems development could be
equated to a production line, where each phase must be planned and carried out before
moving onto the next
...

In the late 1970's and throughout the 1980's, several Japanese companies began using phased
program planning in new product development
...
This led to just-in-time manufacturing and
eventually agile software development
...
But exactly
what is agile development? Put simply, agile development is a different way of managing IT
development teams and projects
...
A small group of people got together in 2001 to discuss their feelings that

the traditional approach to managing software development projects was failing far too often,
and there had to be a better way
...
It says, “we 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 That is, while there is value in the items on the right, we value the items on
the left more
...
From my use of various agile methods, I have written about 10 key
principles of agile
...
They are: 1
...

The team must be empowered to make decisions 3
...
Capture requirements at a high level; lightweight & visual 5
...
Focus on frequent delivery of products 7
...
Apply the 80/20 rule 9
...
A collaborative & cooperative
approach between all stakeholders is essential there are various methodologies that are
collectively known as agile, as they promote the values of the agile manifesto and they are
consistent with the above principles
...
DSDM was around before the term ‘agile’ was even
invented, but is absolutely based on all the principles we’ve come to know as agile
...
Scrum is also an agile development
method, which concentrates particularly on how to manage tasks within a team-based
development environment
...
XP (Extreme Programming) is a
more radical agile methodology, focusing more on the software engineering process and
addressing the analysis, development and test phases with novel approaches that make a
substantial difference to the quality of the end product
...
Over the last 10 years, there is an ever-increasing
volume of success stories, where companies have dramatically improved the success and
performance of their IT development teams and projects
...
In reality, though, agile is not a magic bullet for all software development
issues
...
To do this reliably with any degree of success really

requires a lot of experience and skill
...
Agile
development can be a very exciting and invigorating approach, although some projects suit
agile more than others
...
Agile development can be
a lot more enjoyable than the waterfall approach, which requires lots more documentation
and is less flexible by its nature
...
Software is developed in
incremental, rapid cycles
...
Each release is thoroughly tested to ensure software
quality is maintained
...
Extreme Programming (XP) is
currently one of the most well known agile development life cycle model
...

Welcome changing requirements, even late in
development
...

Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale
...

Build projects around motivated individuals
...

The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation
...

Agile processes promote sustainable development
...


Continuous attention to technical excellence
and good design enhances agility
...

The best architectures, requirements, and designs
emerge from self-organizing teams
...




---