null
US
Sign In
Sign Up for Free
Sign Up
We have detected that Javascript is not enabled in your browser. The dynamic nature of our site means that Javascript must be enabled to function properly. Please read our
terms and conditions
for more information.
Next up
Copy and Edit
You need to log in to complete this action!
Register for Free
6412284
Introduction to Agile
Description
Graduate diploma Graduate Diploma in Computing (Agile) Mind Map on Introduction to Agile, created by Freda Fung on 21/09/2016.
No tags specified
project management
agile
graduate diploma in computing
agile
graduate diploma
Mind Map by
Freda Fung
, updated more than 1 year ago
More
Less
Created by
Freda Fung
about 8 years ago
84
1
0
Resource summary
Introduction to Agile
Visioin Statement
Annotations:
For (customer) Who (statement of the need) The (product) IS AN (product Category) THAT (key benefit) UNLIKE (key differentiator)
Agile Manifesto
4 Values
Individuals & Interactions
Annotations:
over processes and tools
Working Software
Annotations:
Over comprehensive documentation
Customer collaboration
Annotations:
over contract negotaion
Responding to change
Annotations:
Over following plan
12 Principles
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Business people and developers must work together daily throughout the project
Build projects around motivated individuals. Given them the environment and support they need, and trust them to get the job done.
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. The sponsors, developers, and users should be able to maintain a constant pace indefinitely
Working software is the primary measure of progress
Continuous attention to technical excellence and good design enhances agility
Simplicity - the art of maximizing the amount of work not done - is essential
The best architectures, requirements, and designs emerge from self-organizing teams
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly
Agile vs Waterfall development
Waterfal Development
Linear process
A lot of hand-offs between siloed teams
Large amount of written documentation
Fixes scope, cost, and duration up front
Relies on detailed planning and design up front to reduce risk
Change adverse or costly to change
Relies on project manager to collect project status and report
Value delivered at the end of the project
Problems with traditional development process
Artifact reviews can't prove the product is correct, or measure the project's true progress
Overly precise plans are difficult to change
Unnecessary dependencies cause blocked or delayed work
Business must completely specify the product upfront
Conformance to plan over change and adaptation
Long feedback loops
Impeded innovation
Unnecessary overhead and bureaucracy
Agile Development
An iterative process - delivery regularly
Flexible duration, scope and cost
Little dsign documentation
Relies on frequesnt collaboration and short feedback loop to reduce risk
Status is visible to everyone
Deliver value quickly - within days or weeks
Change is welcome
Drivers for Agile Adoption
Buisiness Enviornment
Annotations:
1.Our business is constantly Changing 2. New ideas emerges constantly 3. Opp. and Threats appear unepectedly
Software Building Process
Annotations:
Solution doesn't always work
Human Behaviour
Annotations:
We misunderstand requirements. When we see something working, we also see improvements
Deliver business value rather than just projects
True Agile Practices
Users are imvolved throughout the process
The team is empowered and allowed to make decisions
While requirements evolve, timelines and timescales are fixed
Annotations:
time duration of each iteration is fixed
All requirements are captured only at a high level, are lightweight, and are generally visually represented
Development proceeds in small incremental steps, each has a release at the end
General focus is always on the frequent delivery of products
At the end of each sprint (iteration), every feature included is complete.
The 80/20 rule is always applied; the focus is on the important 20% that willd rive the majority of the results
Testing is implemented throughtout the lifecycle. Testing is done early and often.
All interactions of the team and stakeholders are collaborative and cooperative.
Benefit of Agile
Faster return on investment through shorter cycles; quicker to market and faster resolution of issues
Increased client confidence by improving productivity; quality and client satisfaction
Happier developers by giving them more autonomy; diversity; and lightweight loads
Better communication with more face-toface; feedback, and collaboration
Better change management
Improved project visibility
Media attachments
15774d86-a361-44bd-9b6c-f9b0ab029cf2 (image/png)
7d437f92-c613-4a94-ac3e-b67b1f3d4e00 (image/png)
7f256a9a-743f-4578-8a60-ee937fb38bf6 (image/png)
Show full summary
Hide full summary
Want to create your own
Mind Maps
for
free
with GoConqr?
Learn more
.
Similar
Agile Practices
Freda Fung
Agile Teams, Work Environment & Scrum Overview
Freda Fung
Expertise in Project Management
tonesha_g
PMP® Pre-Test by Coursefountain.com
Team Coursefountain
Ch1 - The nature of IT Projects
mauricio5509
Introduction notes on SCRUM Project management framework.
Wesley Thomson
Project Management: Week 1
Sharon Ott
Summary of Definitions/Key Terms for the PMP Exam
Andrea Leyden
PMP Prep quiz
Andrea Leyden
06 PROJECT TIME MANAGEMENT
miguelabascal
Project Scope Management Process
neeshar
Browse Library