Agenda/Tasks done 27/9 2012

15
Systems Development Methodology Agile Practices: Shared Vision Informative Workspace Planning the Second Iteration 4. semester autum 2012

description

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) - PowerPoint PPT Presentation

Transcript of Agenda/Tasks done 27/9 2012

Page 1: Agenda/Tasks done 27/9 2012

Systems Development Methodology

Agile Practices: Shared Vision

Informative WorkspacePlanning the Second Iteration

4. semester autum 2012

Page 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

Agenda/Tasks done 27/9 2012

Page 3: Agenda/Tasks done 27/9 2012

Shared Vision Pair Programming Test Driven Development Continuous Integration System Metaphor Sustainable Pace Collective Code Ownership Coding Standard Iterative development (short

iterations with plan) Planning Game Use Case Modelling Whole Team (Onsite Cusomer) Self-organising teams

Selected Agile Practices Risk-Value Lifecycle Acceptance test Simple Design Daily Srum Unit test Small Releases Sprint review Sprint retrospectives Burndown chart – Tracking Estimations Design Improvement (Refactoring) Informative workspace (Scrum

Board) 2 level planning The pomodoro Technique Product Backlog Sprint Backlog

Page 4: Agenda/Tasks done 27/9 2012

The Shared Vision is the product of the first iteration

Page 5: Agenda/Tasks done 27/9 2012

A QA model for developmentAgile Practice: Risk-Value Lifecycle, agile architecture

Demonstrate Understanding of the Problem

Demonstrate Understanding of the Solution

Demonstrate the Solution

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

Page 6: Agenda/Tasks done 27/9 2012

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?

Shared Vision

Page 7: Agenda/Tasks done 27/9 2012

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?

The Vision statement should answer the following questions

Page 8: Agenda/Tasks done 27/9 2012

ITERATIVE & INCREMENTAL

Page 9: Agenda/Tasks done 27/9 2012

Iterative development

Plan (Goals and Vision)analyze

design

Demonstrate with customers

evaluate

Re-plan

This project: iteration cycles: one week

• Develop in frequent, small increments• Demonstrate and learn (constant feedback)• Re-plan

Page 10: Agenda/Tasks done 27/9 2012

Agile Practices in this iteration

•Informative Workspace•Weekly planning•User Stories•Self-organizing teams•Product Backlog•Sprint / Iteration Backlog

Page 11: Agenda/Tasks done 27/9 2012

Informative workspaceSCRUM BOARD

To Do Doing DoneTo dayTask:_______

Estimate:2 hrs

Who:John and Ivy

Page 12: Agenda/Tasks done 27/9 2012

Scrum Board

Page 13: Agenda/Tasks done 27/9 2012

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

Iteration plan – weekly planning

Page 14: Agenda/Tasks done 27/9 2012

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.

The Planning Game

Page 15: Agenda/Tasks done 27/9 2012

Do your planning games

3 meetings to take place

Time? Arrangements?

Project work