1. C O N F I D E N T I A L 4-May-15 1 Attendee Management - Being Agile Attendee Management

2. C O N F I D E N T I A L 4-May-15 2 Agenda New steps towards Agile Benefits Challenges Support

3. C O N F I D E N T I A L 4-May-15 3 New Steps towards Agile Scope management – Single list for everything to-be accomplished – Rank every story (Dev, Support, hot-fix, DR testing) in that iteration – Trade off calls much easier (All dependencies encapsulated in story points) Capacity planning – Focus factor helps depict accurate capacity Unit of measure – DAILY (Check-in DAILY, Write Test Cases DAILY, Build DAILY, Validate DAILY) Daily Standup meeting – Review burn down chart DAILY – High visibility – Call out risks daily No “I” in team – DEV+QA – Requirements, Planning & Estimation – Team decides – Load balance development tasks & QA tasks

4. C O N F I D E N T I A L 4-May-15 4 New Steps towards Agile – Cont. Communication – Face to face, Pick up the phone & Finally, email! – Every story DEV+QA sync up DAILY Weekly Testing – DEV+QA spend an hour weekly – Regression, Functional (Team decides areas to test) Brain storm meeting before sprint planning

5. C O N F I D E N T I A L 4-May-15 5 Benefits Improved DEV+QA partnership Communication – Logistics resolved in daily standup call or on phone Sense of ownership – Solution driven team Leaders emerge in Team – Driving Sales Force Project – Event Marketing – Design/IT co-ordination – PCI Compliance – DM effort + Release Management – QA Automation

6. C O N F I D E N T I A L 4-May-15 6 Benefits (Cont.) Improved Quality (10 day before + after release comparison)

7. C O N F I D E N T I A L 4-May-15 7 Challenges Product management involvement – Lock down release & scope early – Mockups & details in stories Pursuit of perfection – Need to work on discipline of doing things – DAILY (Ex: Rally update) Environments – Need performance environment – Existing environment upgrade Bug tracking – Rally & Test track have to be kept in sync

8. C O N F I D E N T I A L 4-May-15 8 Support One Team – Support + Development Load balance support issues within team Encourages ownership Customer usage visibility – Helps correct test cases + better coding practices Challenges – Support load affects committed deliverables for sprint

9. C O N F I D E N T I A L 4-May-15 9 Q & A