1 / 15

Agenda/Tasks done 27/9 2012

Systems Development Methodology Agile Practices: Shared Vision Informative Workspace Planning the Second Iteration 4. semester autum 2012. Agenda/Tasks done 27/9 2012. User assignments (product owner) ‘circle’ 1 st sprint: Scrum Boards (informative workspace)

kaemon
Download Presentation

Agenda/Tasks done 27/9 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Systems Development Methodology Agile Practices:Shared VisionInformative WorkspacePlanning the Second Iteration 4. semester autum 2012

  2. Agenda/Tasks done 27/9 2012 • User assignments (product owner) • ‘circle’ • 1st sprint: • Scrum Boards (informative workspace) • Product -, release -, sprint -, defect backlog • Burndown charts • Shared vision • User stories • Daily scrum • Planning Game

  3. Selected Agile Practices • Shared Vision • Pair Programming • Test Driven Development • Continuous Integration • System Metaphor • Sustainable Pace • CollectiveCodeOwnership • Coding Standard • Iterative development (short iterationswith plan) • Planning Game • Use Case Modelling • Whole Team (OnsiteCusomer) • Self-organising teams • Risk-ValueLifecycle • Acceptance test • Simple Design • DailySrum • Unit test • Small Releases • Sprint review • Sprint retrospectives • Burndown chart – Tracking Estimations • Design Improvement (Refactoring) • Informative workspace (ScrumBoard) • 2 levelplanning • The pomodoroTechnique • ProductBacklog • Sprint Backlog

  4. The Shared Vision is the product of the first iteration

  5. A QA model for developmentAgile Practice: Risk-Value Lifecycle, agile architecture Demonstrate Understanding of the Solution Demonstrate the Solution Demonstrate Understanding of the Problem Use the Solution Achieve concur-rence among all stakeholders on the lifecycle objectives for the project Baseline the architecture of the system to provide a stable basis for the construction Clarify the remaining requirements and complete the development of the system Ensure that software is available for its end users

  6. Shared Vision Quality Criteria : Are you and your team capable of communicating the shared vision to whom it may concern so that it make sense to all relevant stakeholders ? Can you demonstrate that all stakeholders agree upon the described vision?

  7. The Vision statement should answer the following questions • Problem Statement • Why is it really that we want to start development of this system? The problem(s) behind the problem. • Organizational issues?, Law issues ?, Technical issues? Customer issues?..... • Needs • What does the organization/the customer need in order to meet the issues mentioned above? (not described as technical solutions) • Features • Which features can an IT system provide so that the customer needs are fulfilled? • Stakeholders • Who are the team? Who are the stakeholders? Who are the users? .. • Competences and qualifications • Which competences and qualifications are needed in the team in order to meet this vision?

  8. Iterative & Incremental

  9. Iterative development • Develop in frequent, small increments • Demonstrate and learn (constant feedback) • Re-plan This project: iteration cycles: one week analyze Plan (Goals and Vision) design Re-plan Demonstrate with customers evaluate

  10. Agile Practices in this iteration • Informative Workspace • Weeklyplanning • User Stories • Self-organizing teams • ProductBacklog • Sprint / Iteration Backlog

  11. Informative workspace SCRUM BOARD Task:_______ Estimate: 2 hrs Who: John and Ivy To Do To day Doing Done

  12. ScrumBoard

  13. Iteration plan – weeklyplanning • Be inspired by the iteration plan we used in the XP game • Issues • Communication • Planning • User stories – for inspiration look at youtube. • Estimation • Velocity • Prioritization

  14. The Planning Game • The game is a meeting that occurs once per iteration, typically once a week. • It is focused on determining what requirements are included in the next iteration. The customers and developers are both part of this. • The customer will provide a short list of high-value requirements for the system. These will be written down on user story cards. • Users and developers will commit themselves to the functionality that will be included and the date of the next release. • Plan the activities and tasks of the developers. • The requirement will be translated to different tasks. The tasks are recorded on task cards. • The tasks will be assigned to the programmers and the time it takes to complete will be estimated. • The tasks are performed and the end result is matched with the original user story.

  15. Project work • Do your planning games • 3 meetings to take place • Time? Arrangements?

More Related