iAgile – iNetFrame’s framework for agile development Features Get to see a working product early Development shadows evolving requirements Pair programming Continuous integration Test driven development Constant refactoring Frequent inspections On time delivery Based on scrum framework

iAgile – Team structure Client Project Sponsor Project coordinator

iAgile – The PDCA (Plan-Do-Check-Act) approach PlanDaily ScrumReviewRetrospect Refine Project sponsor, teamTeam Stakeholders, Project sponsor, team Team PlanDaily ScrumReviewRetrospectRefine Project sponsor & team negotiate what PBIs the team will complete in this sprint and prioritize. The sprint duration is typically 2-4 weeks. The team decomposes the PBI into Sprint tasks (16 hours to plan a sprint) Each developer updates the team on the progress, impediments and the plan for the day Review sprint tasks, burndown chart & impediments At the end of a sprint, the team demonstrates the working product increment Sponsor declares PBIs as done according to the negotiated agreement Incomplete PBIs, feedback go into the PBI again Lessons learnt and process improvement What has gone well and what has not? What are the impediments, what action needs to be taken? Team further decomposes PBI. Write new / Revise functional specifications (stories) and estimates effort for the PBIs Sponsor prioritizes the PBIs before the next Planning meeting

iAgile – The Product Backlog Item(PBI) & Sprint tasks PBI is a ranked list of desired functionality for the product. Each PBI is required functionality in the form of a narration (a user story). The focus is on answering “what” and not “how” of the requirements Each PBI will have an acceptance criteria and an estimated effort The PBI is broken into sprint tasks in a manner that a sprint task can be completed within a day, leading to daily integration, build and release Sprint task specifies the “How” to achieve the PBI’s “What” High priority Product backlog item 1 Product backlog item 2 Product backlog item 3 Product backlog item 4 Product backlog item 5 Product backlog item 6 Product backlog item RB1 Product backlog item RB2 Low priority Release backlog Product backlog item 1 Sprint task 1 Sprint task 2 Sprint task n

iAgile – the Sprint Board Committed PBISprint tasks not startedSprint tasks in progressSprint tasks completed Day

iAgile – Burndown charts Sprint Burndown chart Total remaining team task hours in one sprint This is revised daily, may go up before coming down Product /Release Burndown chart Product backlog remaining effort from one sprint to the next Depicts emperical trends – a reality check to the sponsor’s release plan

iAgile – Selection criteria Uncertain requirements Cross functional teams High on communication demands Requirement of high visibility High on trust High risk The expectation of a working product demonstrated early Pricing model : T & M ???