Agile Development at W3i
Download as PPTX, PDF0 likes551 views
Agile development methodology focuses on iterative development where requirements and solutions evolve through collaboration between cross-functional teams. Some key aspects of agile include short development cycles, working software over documentation, customer collaboration, and responding to change. Scrum is a popular agile framework used at W3i that utilizes user stories, estimating, planning meetings, daily stand-ups, burndown charts, sprints, reviews and retrospectives to deliver working software frequently.
More Related Content
What's hot (20)
Similar to Agile Development at W3i (20)
More from Jeff Bollinger (7)
Agile Development at W3i
- 1. Agile Development MethodologyJeff BollingerVP of Information Systemsjeff.bollinger@w3i.com @Jbollingerwww.jeffbollinger.netSt. Cloud State UniversityIS 350 10.13.2010
- 3. Whats a Development Methodology?A process or methodical approach to developing software. A repeatable process used to:Handle RequirementsImprove QualityManages Risk
- 4. Examples of MethodologiesWaterfallAgileScrum W3is FlavorXPKanban
- 6. Waterfall Works Well WhenRequirements are stableTechnology is well known and matureEverything happens as one would expectWe are not taking on anything new or unknownWe have done this many times before
- 7. WaterfallThe Real WorldRequirementsChangeDesignImplementationTakes too longTestingGets skippedDeploymentMaintenance
- 8. What is Agile?Agile software development油refers to a group of油software development methodologies油based on iterative development, where requirements and solutions evolve through collaboration between self-organizing油cross-functional teams.
- 9. The Agile ManifestoWe are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and tools Working softwareover comprehensive documentationCustomer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.http://agilemanifesto.org/
- 10. Agile PrinciplesOur highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- 11. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
- 12. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
- 13. Business people and developers must work together daily throughout the project.Agile PrinciplesBuild projects around motivated individuals. Give them the environment and support they need, and trust them to get the jobdone.The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.Working software is the primary measure of progress.Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
- 14. Agile PrinciplesSimplicity--the art of maximizing the amount of work not done is essential.Continuous attention to technical excellence and good design enhances agility.The best architectures, requirements, and designs emerge from self-organizing teams.At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
- 15. Why Agile?
- 16. The Agile Paradigm ShiftWaterfallAgileFixedRequirementsResourcesTimePLANDrivenVisionVALUEDrivenEstimatedFeaturesResourcesTime
- 17. What is Scrum?Scrum油is popular flavor of agileUsed @ W3i for past 5 years
- 19. ScrumPlanning MeetingUser StoryBurndown ChartEpicsRetrospectiveReview MeetingStory PointsEstimatingTasksBacklogVelocity
- 20. User StoriesA software requirement formulated as one or two sentences in the everyday business language of the userFormat: As a (role) I want (something) so that (benefit)Example: As a customer service representative, I want to search for my customers by their first and last name, so that I can spend less time browsing lists.
- 21. EstimatingA consensus-based estimation methodEstimate effort or relative size of development tasks Estimate in Story PointsStory points possibilities are 0,1,2,3,5,8,13
- 22. VelocityNumber of story points completed in one sprint (iteration)Calculated by taking the last three sprints rolling average
- 23. Planning MeetingApproximately one dayIncludes Development Team and Business OwnersPull prioritized stories from the backlog and technically plan themCall in business owners to clarify requirementsDatabase design ERDAPI SpecificationsBreak stories down into several tasksCommitment is made to Business Owners to deliver stories by end of the sprint
- 24. Daily ScrumStand-up meetingNot longer than 15 minutesEach developer answers 3 questions:What did you work on yesterday?What are you going to work on today?What are your roadblocks, if any?
- 25. BurndownIllustrates the progress of the current sprint.
- 26. Sprint ReviewsOccurs at the end of every sprint Business owners and Development Team are presentDemonstration of working software is given by the development team
- 27. RetrospectivesLearningContinuous ImprovementMeeting with product management, team members, managersDiscussion on successes and areas for improvement in the current sprint
- 28. Questions?Jeff BollingerVP of Information Systemsjeff.bollinger@w3i.com