By Manish Shrotriya CSE MS 4 Point Agile Manifesto 1.Individuals and interactions over processes and tools 2.Working software over comprehensive documentation 3.Customer collaboration over contract negotiation 4.Responding to change over following a plan

By Manish Shrotriya CSE MS Agile in Practice 1.Customer: Actual customer, Customer Representative, Someone who could be involved closely, BA 2.Developers: programmers 3.Quality Analyst(QA): Team Members who will define user acceptance test cases for stories 4.User Stories: Broad requirements are captured and broken into user stories that can be finished in 3-5 days (Story Points based on working hrs.) (45 mins.) 5.Iteration: unite of planning (2 week)

By Manish Shrotriya CSE MS Agile in Practice 6.Team Leader: Team facilitator (management of stories) 7.Acceptance Tests: list of tests against every user story, passing these tests means story is delivered. With each story in play, test suite grows. Once passed never allowed to fail. 8.Technical Leader: Keep track of technical requirements and how things are being developed 9.Pair Programming: Coding is done in pairs, fun and extreme code review. Reduces defects.

By Manish Shrotriya CSE MS Agile in Practice 10.Tasks: Tasks completed by a pair to complete a story 11.TDD: write a test, it will fail. Write the code to pass tests. Extreme Testing, (in Pair Programming) 12.Velocity: Total story points delivered in one iteration, could be different than the story points, any iteration starts with. 13.Collective Ownership: Everyone works one every module during the one release.

By Manish Shrotriya CSE MS Agile in Practice 14.Release Plan: Collection of stories played by the team with a given period. Usually 3 months 15.Continuous Integration: Multiple check-ins normally task based, on every check-in entire project is automatically built. 16.Sustainable Pace: marathon not a 100mtr sprint. Every day work for defined hrs. only. 17.Open workspace: no cubicles, improved interaction, like a bazar (room full of conversation buzz)

By Manish Shrotriya CSE MS Agile in Practice 14.Simple Design: Worry about current stories only Leave hooks for future technology DRY (Don’t Repeat Yourself)

By Manish Shrotriya CSE MS Agile in Practice: Planning (the game) 1.Exploration: Customer and Developers together Identify all the significant features For each feature, break it into user stories Estimate user story, neither too large nor too small guideline is smallest atomic piece of work. Large stories are broken into smaller and re-estimated. Customer prioritizes the stories

By Manish Shrotriya CSE MS Agile in Practice: Planning (the game) Iteration Execution: Developers and Customer Select Team leader Select stories to be played in the current and next iteration Review of last iteration: calculate actual and average velocity Failed stories from last iterations are included

By Manish Shrotriya CSE MS Agile in Practice: Planning (the game) Iteration Execution: Developers Make pairs Pick stories Identify Tasks QA Write test for stories to be played in next iteration Test Stories delivered in previous iteration Both roles will played by everyone.

By Manish Shrotriya CSE MS Agile in Practice: Planning (the game) 1.Task till Thursday 1.Git familiarization 2.Bundle knowledge 3.Gems knowledge