#t3scrum: 12 principles of agile
DESCRIPTION
This is one hour free webinar about Agile principles for software development. Main purpose for this webinar is to give attendees overview of Agile methodology for software development and provide understanding of main Agile principles.TRANSCRIPT
About us
● #T3SCRUM○ t3scrum.com○ buzz.typo3.org/teams/agile/○ facebook.com/T3SCRUM○ @t3scrum
● Andriy Kushnarov○ [email protected]○ facebook.com/akushnarov○ @akushnarov
Agenda
● Introduction● Agile and other methods● Agile manifesto● 12 principles of Agile● Agile values
Your Questions will be covered● What are some ideas for engaging customers during Agile development?● Just looking for a general introduction to the topic.● How to sell agile projects● i dont know agile because work with waterfall● Agile advantages.● Agile disadvantages.● What are the general concepts behind Agile?● Which types of projects (or maybe departments of IT industry) are the most
appealing to Agile?● It'll be great if the presenter mentioned the some common mistakes that
we need to avoid● Please tell about Agile software development for newbies● How to help my boss understand that agile is good?● ...
What is Agile?
https://www.google.com/?q=what+is+agile
Agile family
http://en.wikipedia.org/wiki/Agile_software_development#Agile_methods
Which method to apply?
Ralph Stacey's complexity matrix
WaterfallAgile
Chaos
Agile vs. Waterfall
http://www.mountaingoatsoftware.com/blog/agile-succeeds-three-times-more-often-than-waterfall
Waterfall
Time: 3-12 month
Waterfall
Time: 3-12 month
Time to fix: X days
Waterfall
Time: 3-12 month
Time to fix: ??
Waterfall
Time: 3-12 month
Time to fix: Y months / years
Time = Money
Waterfall
Time: 3-12 monthREVENUE
Agile and waterfall
Agile
Time: 2-4 weeks
Feedback
Agile
Time: 2-4 weeks
Feedback
Time to fix: 2-4 weeks
Agile
Time: 2-4 weeks
Feedback
Time to fix: 2-4 weeks
REVENUE
12 principles of Agile
#1 Our highest priority is to satisfy the customerthrough early and continuous deliveryof valuable software.
12 principles of Agile
#2 Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
12 principles of Agile
#3 Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
12 principles of Agile
#4 Business people and developers must work together daily throughout the project.
12 principles of Agile
#5 Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
12 principles of Agile
#6 The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
12 principles of Agile
#7 Working software is the primary measure of progress.
12 principles of Agile
#8 Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
#9 Continuous attention to technical excellence and good design enhances agility.
12 principles of Agile
12 principles of Agile
#10 Simplicity - the art of maximizing the amount of work not done - is essential.
12 principles of Agile
#10 Simplicity - the art of maximizing the amount of work not done - is essential.
12 principles of Agile
#11 The best architectures, requirements, and designs emerge from self-organizing teams.
12 principles of Agile
#12 At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
http://en.wikipedia.org/wiki/Kaizen
Agile values
Agile values
● Commitment● Openness● Focus● Respect● Courage
Is Agile a silver bullet?
When Agile does not work?
● Lack of support of Agile● Lack of responsibility● Lack of trust● Lack of communication
Thank you!What's next?● Help us to improve, please provide
feedback: bit.ly/Y9rq7N
● Next webinar topic:on.fb.me/17r2Ba3
Follow us: @T3SCRUMFacebook: T3SCRUM