I agila projekt försöka man slippa undan commitmentsEn sprint i taget bara
Definition of Done
Never blame the tool!
Adform – we did it and we are Lithuanians!
It is not just simple Scrum rules or iterations
Define the goal, and measure against it!
Transcript of "Agile and Agile methods: what is the most important to understand to succeed"
Agile and Agile methods: what is the most important to understand to succeed<br />Vaidas Adomauskas<br />
Disclaimer<br />This is just my opinion and interpretation of information<br />Use at your own risk ;)<br />Information and pictures from<br />Henrik Kniberg<br />Mary Poppendieck<br />Google<br />...<br />
About me (1)<br />VU MIF – Software Engineering(bachelor)<br />IT University of Gothenburg – Master in Software Engineering and Management<br />Lavasoft(www.lavasoft.com )<br />Adform (www.adform.com)<br />
Apie mane (2)<br />Certified Scrum Master (Ken Schwaber, Paris)<br />Certified Product Owner (Robin Dymond ,Kiev)<br />Agile Conferences<br />http://scrum.agile.lt<br />Lecturer at VU MIF “Agile Project Management with Scrum”<br />
Magic word?<br />Traditional Process and Statistics<br />Agile<br />
Traditional SW projects are like a cannon ball<br />Assumptions:<br />The customer knows what he wants<br />The developers know how to build it<br />Nothing will change along the way<br />
We tend to build the wrong thing<br />This graph courtesy of Mary Poppendieck<br />The Biggest Opportunity to Increase Software Development Productivity is to Write Less Code!*<br />*Mary Poppiendieck, “It’s Not About Working Software”, Agileee 2010 conference<br />12<br />
Maybe we are successfull?<br />“The primary reason [for the improvement] is that projects have gotten a lot smaller.”<br />“Doing projects with iterative processes as opposed to the waterfall method, which called for all project requirements to be defined up front, is a major step forward.”<br />Jim Johnson<br />Chairman of<br />Standish Group <br />“There is no silver bullet but agile methods come very close”<br />Sources:<br />http://www.softwaremag.com/L.cfm?Doc=newsletter/2004-01-15/Standish<br />http://www.infoq.com/articles/Interview-Johnson-Standish-CHAOS<br />”My Life is Failure”, Jim Johnson’s book<br />13<br />
How about performance of Agile?<br />Source: Dr. Dobb’s Journal 2008 Agile Adoption Survey<br />
Avoid bugs (1972)<br />“Those who want really reliable software will discover that they must find means of avoiding the majority of bugs to start with…<br /> … programmers… should not introduce the bugs to start with.”<br />Edsger W. Dijkstra, “The Humble Programmer”, 1972 (http://userweb.cs.utexas.edu/~EWD/transcriptions/EWD03xx/EWD340.html)<br />
The Life Cycle Concept (1976)<br />The biggest opportunity for cost reduction was finding errors as soon as possible:<br />Barry W. Boehm, “Software Engineering”, 1976 (http://www.computer.org/portal/web/csdl/doi/10.1109/TC.1976.1674590)<br />
Problem 1<br />Separation of design from implementation<br />Swartout and Balzer: “All current software methodologies have adopted a common model that separates specification from implementation. Unfortunately, this model is overly naïve, and does not match reality.”*<br />*Swartout and Balzer, “On the Inevitable Intertwining of Specification and Implementation”, 1982<br />
Problem 2<br />Large batchesof work (usually all project)<br />“Large batches of work tend to queue up during each process step, and so defects are not detected at the point of insertion; they have to wait to be uncovered in a batch validation step”<br />*Mary and Tom Poppiendieck, “Leading Lean Software development”, 2000<br />
Other opponents<br />McCracken and Jackson, “Life Cycle Concept Considered Harmful”, 1982<br />Tom Gilb, “Evolutionary Development”, 1981<br />Start with short measurable business goals<br />Incremental deliverables (real software, real value)<br />Toyota Way<br />Just In Time (JIT)<br />Lean<br />Agile<br />….<br />