CSE 300 2014 MS Feb 2001 Enough of

CSE 300 2014 MS Feb 2001 Enough of Documentation & failures 17 Guys met came up with following 4 Agile Principles 1. 2. 3. 4. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan By Manish Shrotriya

CSE 300 2014 MS Individuals and interactions over processes and tools Lets think about a Soccer Team We had excellent players We had the best coach, who has great discipline and training capabilities. We daily practiced hard Still we lost the tournament ? By Manish Shrotriya

CSE 300 2014 MS Individuals and interactions over processes and tools Great IDE, powerful language, best version control Hierarchy of Experts, regular promotions, Strict job description What could go wrong? By Manish Shrotriya

CSE 300 2014 MS Individuals and interactions over processes and tools 1. Strong player An ace programmer with ego or an average programmer with cooperative attitude. 2. Use tools only when you think you really need it 3. Work to create the team and then let the team configure the environment on the basis of need By Manish Shrotriya

CSE 300 2014 MS Working Software over Comprehensive Documentation Too much documentation V 1 of ABC has very detailed documentation. Problem? Too little documentation Anything good about it? By Manish Shrotriya

CSE 300 2014 MS Working Software over Comprehensive Documentation Effective document Ex: Alt key press, good comment Best document Code and team By Manish Shrotriya

CSE 300 2014 MS Working Software over Comprehensive Documentation Best document Code and team, Alt key press, good comment Write a document when • there is value in the document • there is a business need • there is a regulatory need • there is a contractual need By Manish Shrotriya

CSE 300 2014 MS Customer Collaboration over Contract Negotiation You have a broken Notebook. Customer support options: phone, email, chat Prefer which one and why? Response is based on Customer type? By Manish Shrotriya

CSE 300 2014 MS Customer Collaboration over Contract Negotiation Software is not a commodity Reason: Failures told us that well described Software requirement on fixed price and schedule cannot produce the right software. Ex. Workshop Successful projects Involve: customer feedback on a regular and frequent basis By Manish Shrotriya

CSE 300 2014 MS Responding to Change over Following a Plan Ex: You have open a Company Car service center. Car company offers free service plan, how to do it? Pick up scenario? Replacement vehicle? Dent Repair? By Manish Shrotriya

CSE 300 2014 MS Responding to Change over Following a Plan The course of a software project cannot be planned very far into the future? 1. Changing business environment 2. Once they see the system start to function, customers are likely to alter the requirements 3. We are not very good at estimating how long it will take to develop them. By Manish Shrotriya