Presenter:Mohit Dhagat Student ID: Date:19 November 2014

Deliver games/apps in a very short development cycle. Stakeholder requirements change very frequently. New games/apps are developed using only internal experience and market research. Customer demands & asks on an existing games/apps are highly unpredictable. Varying budgets throughout FY. 3 of 7

Agile approach to development Top priority is to keep their users satisfiedWelcome changes in requirements at anytimeSimplicity is keyAligns strategically across the companyEasier collaboration and partneringHaving more face-to-face communicationEfficient feedback-loop system Push approach to management Work Items (tasks or bugs) are in the Product Backlog Work Items are prioritised by Program Managers Work Items are then ‘pushed’ to developers and/or testers by Dev and/or Test Lead Each individual now has a queue of stack ranked work items to work over sprint 4 of 7

5 of 7 Phase Type What happens in this phase? Concept (Iteration -1) Brainstorming the game/app (Ideation) & project budget approvals by SLT. Inception (Iteration 0) Initiate designing & prototyping the game/app. Development Iterations Developing & Testing the game/app in multiple iterations. Transition (Release) Deploying release v1 to PROD from PPE & starting work on v2. Production Launch, Operate, Maintain and Support v1 across launch markets. Retirement Remove v1 from PROD and/or upgrade to v2.

‘Traditional’ Agile methods doesn’t translate entirely in software dev. Principles & practices do translate entirely in software dev. Almost all teams in Microsoft follow an Agile SDLC. It enables teams to be quicker, smarter, flexible and efficiently respond to stakeholder changes. The opportunity for teams to be leaner is very slim. Teams should try to adopt the pull model instead of push. Management techniques can vary significantly depending on team dynamics. 6 of 7

7 of 7