Agile.txt
1
Agile: Can softwear development fast Incremental Iterative: Sketch No role/need for managers,team is self organizing No need for planning No documentation/discuss and develop No design Agile Manifesto Format of X over Y more valuable Individual and Interaction over Processes and tools Agile leader guides teams to interact rather giving direction Working Software over comprehensive documentation Customer Collaboration over contract negotiation Responding to change over following a plan rather than writing elaborate documentation develop Slice oof the functionality and show to user and take feedback Disadvatage :Creates long inventory in process inventory Disadvantage with comprehensive documentation can elaborate it as his perception can differ from those who develop it disad:done with documentation we think we are done with 20% work Customer who gives us scope we give return as software Agile say dont look in those boundaries see what is needed by end users Customer tries to elaborate ,we needs to be party for what is needed by end user Contract should be a facilitator Responding to change when we make a plan we think sequence of activities we should look for rolling wave planning we shall elaborate as time goes When we have change requet we think of replan We have not thought of elaborative steps discuss the development which we can do we do a rolling wave planning We need to relook our plan when it is not working which is different in traditional where we check on execution Perpection: Deliver value fast [email protected]
description
Understanding Agile
Transcript of Agile.txt
Agile: Can softwear development fastIncrementalIterative: SketchNo role/need for managers,team is self organizingNo need for planningNo documentation/discuss and developNo design
Agile ManifestoFormat of X over Y more valuableIndividual and Interaction over Processes and tools Agile leader guides teams to interact rather giving directionWorking Software over comprehensive documentationCustomer Collaboration over contract negotiationResponding to change over following a plan
rather than writing elaborate documentation develop Slice oof the functionality and show to user and take feedbackDisadvatage :Creates long inventory in process inventoryDisadvantage with comprehensive documentation can elaborate it as his perception can differ from those who develop itdisad:done with documentation we think we are done with 20% workCustomer who gives us scope we give return as softwareAgile say dont look in those boundaries see what is needed by end usersCustomer tries to elaborate ,we needs to be party for what is needed by end userContract should be a facilitator
Responding to change when we make a plan we think sequence of activitieswe should look for rolling wave planning we shall elaborate as time goesWhen we have change requet we think of replanWe have not thought of elaborative stepsdiscuss the development which we can do we do a rolling wave planningWe need to relook our plan when it is not workingwhich is different in traditional where we check on execution
Perpection:Deliver value fast
