William Raymond
Juan Navarro
Khalid Mudawe
5359
Cisa Project Manage
ment
Dr Barbara Hewitt
April 26 2010
Pe o p l e i n h i s t o r y t h a t i n s p i re d D i ff e re n t m e t h o d s & g a v e u s m u c h o p p o r t u n i t y t o b u i l d f ro m
Frederick Winslow Taylor born in 1856
I Applied the scientific method to the management of workers greatly could improve productivity
I simplified jobs for unskilled workers
Ibn al-Haytham aka (al-Basri) born in Alhazen, 965–1039
I’m one of the key figures in the development of scientific method
I also Seek Truth
OVERV IEW
introduction
Benefits
Agile Vs Traditional
Disadvantages
philosophy
Scrum
Conclusion
IntroductionIn general, unlike traditional linear (waterfall) development,
Agile methods seek to break down organizational barriers and drive toward faster incremental development and
deployment, without compromising the quality of the delivered product. Agile is focused on individuals and interactions over processes and tools, yet contrary to some (widely
held) beliefs, “true” Agile Development is extremely structured and disciplined, and typically will only succeed in higher maturity organizations
History of the Agile Methodology? The modern definition of agile software development evolved
in the mid-1990s as part of a reaction against "heavyweight" methods, perceived to be typified by a heavily regulated, regimented, micro-managed use of the waterfall model of development. The processes originating from this use of the waterfall model were seen as bureaucratic, slow, demeaning, and inconsistent with the ways that software developers actually perform effective work. Initially, agile methods were called "lightweight methods.“
In 2001, 17 prominent figures in the field of agile development (then called "light-weight methods") came together at the Snowbird ski resort in Utah to discuss ways of creating software in a lighter, faster, more people-centric way. They coined the terms "Agile Software Development" and "agile methods", and they created the Agile Manifesto, widely regarded as the canonical definition of agile development and accompanying agile principles. Later, some of these people formed The Agile Alliance, a non-profit organization that promotes agile development.
http://en.wikipedia.org/wiki/Agile_software_development
What Is Agile Methodology?Although there are many differing approaches to Agile
Development, there are a number of shared characteristics that generally apply. These are:
Agile Development Methodology is an approach to software development that values early and continuous delivery of production ready software in a structured, systematic and repeatable wayAt its core, Agile focuses on the efficiencies that are natural to small teams that have well defined roles and responsibilities. The goal is to have a process that enables the highest percentage of project effort to be spent on building quality components while avoiding all extraneous stepsFrequent delivery of proven production ready software is the single most important measurement of progress
Development iterations that are most typically between 2 and 6 weeks in lengthoStrict adherence to:
Iteration start and end dates Iteration deliverables which include (not
necessarily in this order) Requirements gathering and analysis Planning Design Development/Build Testing Deployment Documentation
Delivering production ready software (iteration end dates are not milestones)
Agile Methodology, cont.
Embracing requirements changes at all times during the project but locking requirements once they are included in an iteration
Using each completed iteration as a mechanism to reprioritize business requirements
Continuous face-to-face interaction with requirements drivers whether they be clients, business partners, or subject matter experts
A common theme among team members, which strives for the most simplistic solution to a given problem. These typically focus on specific problems which are real today and do not attempt to address problems which may occur in the future.
Continuous re-evaluation of the methodology, the procedures, the code. Everything should be frequently re-evaluated for inefficiencies and updated to reflect the current team, department, company, and industry environments.
Agile Methodology, cont.
Principles behind the Agile Manifesto
Welcome changing requirements
Deliver working software frequently
Work together
Build projects around motivated individuals.
Principles behind the Agile Manifesto continued
face-to-face conversation
Working software is the primary measure of progress.
Continuous attention to technical excellence and good design enhances agility.
Principles behind the Agile Manifesto #3Simplicity
self-organizing teams.
tunes and adjusts its behavior accordingly.
The Agile Values
We are uncovering better ways of developingsoftware by doing it and helping others do it.Through this work we have come to value:
• 1Individuals and interactions over processes and tools
• 2Working software over comprehensive documentation
• 3Customer collaboration over contract negotiation
• 4Responding to change over following a plan
What is Scrum?
Scrum is an
iterative, inc
Remental
rapidly and repeatedly
shortest time
Scrum origins Jeff Sutherland
Initial scrums at Easel Corp in 1993 IDX and 500+ people doing Scrum
Ken Schwaber ADM Scrum presented at OOPSLA 96 with
Sutherland Author of three books on Scrum
Mike Beedle Scrum patterns in PLOPD4
Ken Schwaber and Mike Cohn Co-founded Scrum Alliance in 2002,
initially within the Agile Alliance
Who has used Scrum?
S t a r t w i t h P r o d u c t
Feature request from Product X
Product backlog
List of features
Master list
Collection
Allowed to grow and change
Key people and jobs
tools they need
Scrum team Project Team.
Small but with a punch
Easy to manage
Everyone gets to know one another
Other key people
Users
Developers and Testers
Re lease p lann ing
Estimated guess of 500 hours ?
Experts are not perchingthe product owner and team identify the features they want
Sprints
Sprints are short duration milestone
4 or more sprints
Release cycles and sprints
have a positive correlation relationship
Burndown chart
Source -http://weblogs.asp.net/jcogley/archive/2008/03.aspx
Burndown velocity
ON time
Process
Product Backlog
The sprint backlog
Daily Scrum meeting
Potentially shippable product increment
Typically meeting setting that don’t utilize scrum methods
People get distracted easily
No one is on the same page
People are not focused
People have different thoughts going on
Scrum method
No chairs
15 minute rule
The purpose of the Daily Scrum meeting is to answer Scrum’s three questions
1
2
3
Today the world is going to Bailout another investment bank!
Conclusion & References http://www.netmba.com/mgmt/scientific/
http://en.wikipedia.org/wiki/Scientific_method
http://www.youtube.com/watch?v=Q5k7a9YEoUI&feature=PlayList&p=24532B7471176794&playnext_from=PL&index=0&playnext=1
http://www.scrumalliance.org/learn_about_scrum
www.agilemanifesto.org/
The END