Scrum Kandidatprojekt datateknik - TDDD83



Similar documents
Agile Project Management By Mark C. Layton

PLM - Agile. Design Code Test. Sprints 1, 2, 3, 4.. Define requirements, perform system design, develop and test the system. Updated Project Plan

Capstone Agile Model (CAM)

Issues in Internet Design and Development

26 May 2010 CQAA Lunch & Learn Paul I. Pazderski (CSM/CSP, OD-CM, CSQA) spcinc13@yahoo.com Cell: AGILE THROUGH SCRUM

Sweden National H.O.G. Rally July 2010

Introduction to Agile and Scrum

LEAN AGILE POCKET GUIDE

Scrum methodology report

Gothenburg 2015 Jan Marek com CA Technologies Introducing Agile development methodologies to Session S601 mainframe development teams

So#ware Development Methodologies Project Management Phases Agile Methodology Agile Manifesto Roles. Team Roles and Responsibili?

3gamma Från traditionell IT-leverans till modern, processtyrd tjänsteleverans i en multi-sourcing miljö. Peter Wahlgren, September 2013

Introduction to Agile Software Development Process. Software Development Life Cycles

D25-2. Agile and Scrum Introduction

How to manage agile development? Rose Pruyne Jack Reed

Governments information technology

Introduction to Agile Scrum

AGILE & SCRUM. Revised 9/29/2015

Information Meeting FACULTIES OF HUMANITIES AND THEOLOGY

Scrum. SE Presentation. Anurag Dodeja Spring 2010

Microsoft SQL Server 2012: Designing Buisness Intelligence Solutions

Applying Agile Project Management to a Customized Moodle Implementation

The Agile Manifesto is based on 12 principles:

FN:S RAPPORT OM E- GOVERNANCE Med lite jämförelser med 2012

Agile Development in Today s Industry. Duke CS408 Session 2014

WELCOME TO. Information Integration

SESSION 303 Wednesday, March 25, 3:00 PM - 4:00 PM Track: Support Center Optimization

SECC Agile Foundation Certificate Examination Handbook

History of Agile Methods

KINAR13h, KINLO13h. The marking period is, for the most part, 15 working days, otherwise it s the following date:

Agile in a Safety Critical world

Atern The latest version of the DSDM approach which makes DSDM appropriate to all types of project.

Viktigaste uppgift: Web Browser SSO

CHAPTER 3 : AGILE METHODOLOGIES. 3.3 Various Agile Software development methodologies. 3.4 Advantage and Disadvantage of Agile Methodology

Waterfall to Agile. DFI Case Study By Nick Van, PMP

Introduction to Agile Software Development. EECS 690 Agile Software Development

Agile in Financial Services A Framework in Focus

Business Model Transformation. Pioneering Business Models through Business Architecture Transformation

T14 "TIMELINES, ARTIFACTS AND OWNERS IN AGILE PROJECTS" Hubert Smits Rally Software Development BIO PRESENTATION 6/21/2007 1:30:00 PM

Agile Training Portfolio

Agile Development Overview

Agile Extension to the BABOK Guide

International Council on Systems Engineering. ISO/IEC/IEEE SEminar Linköping 16 november 2015

Role of the Business Analyst in an Agile Project

Agile Processes and Distributed Projects: Dream or Nightmare?

Iteration Planning. also called Iteration Kickoff

Agile Scrum Workshop

Marknadsföring som en del av intäktsprocessen.

Introduction to Agile

IMQS TECHNOLOGY AGILE METHODOLOGY

Introduktion till SAS 9 Plattformen Helikopterkursen

Neglecting Agile Principles and Practices: A Case Study

Agile So6ware Development

5 Levels of Agile Planning: From Enterprise Product Vision to Team Stand-up

The traditional project management uses conventional methods in software project management process.

Agile Development with C#

SCRUM BODY OF KNOWLEDGE (SBOK Guide)

Elektronikavfall. Thomas Lindhqvist IIIEE Lund University. 18 February 2009

Agile letvægts projektstyring med Google PROSA, 31/ Thomas Blomseth, BestBrains

TSG Quick Reference Guide to Agile Development & Testing Enabling Successful Business Outcomes

Scrum is an efficient framework within which you can develop software with teamwork. It is based on agile principles.

Secrets of a Scrum Master: Agile Practices for the Service Desk

Microsoft + SOA = Sant? Joakim Linghall Principal System Engineer SOA and Business Process joakiml@microsoft.com

Developing the Agile Mindset for Organiza7onal Agility. Shannon Ewan Managing

Agile Systems Engineering: What is it and What Have We Learned?

Atomate Development Process. Quick Guide

Scrum Guidelines. v W W W. S C R U M D E S K. C O M

Repetition inför tentan. Kommunikation. Infrastruktur. ÖP Inga hjälpmedel. v v v

The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. July Developed and sustained by Ken Schwaber and Jeff Sutherland

Intrepid Travel Language Guides

Agile Project Management: Adapting project behaviors to the software development environment

Water-Scrum-Fall Agile Reality for Large Organisations. By Manav Mehan Principal Agile consultant

Would you like to have a process that unlocks ability to learn and produce faster?

How To Get Healthy With A Game Called Angel Hour

Teaching an Elephant to Dance. Patterns and Practices for Scaling Agility

Creating a High Maturity Agile Implementation

Agile Teams and Architecture. Tommy Ågren

The Agile Project Manager

The Agile Glossary of Terms

Certified Scrum Master Workshop

Agile Scrum and PMBOK Compatible or Contrary?

SCRUM. A Tool from the Software World Can Improve Analytical Project Outcomes. By KyMBER WALTMUNSON

Comparative Study of Agile Methods and Their Comparison with Heavyweight Methods in Indian Organizations

Agile Project Management

Thomas Arctaedius Ph D Nuclear Physics Started 8 companies (3 sold, 2 dead, 3 alive) CEO and chairman Visiting scholar Stanford University

Agile with XP and Scrum

AGILE - QUICK GUIDE AGILE - PRIMER

Experiences Linking Business Architecture with an Agile/Lean Development Method

"Bezpieczny Projekt"

How NOT to Do Scrum. Patterns and Anti-patterns. Revised July First presented at New York City Scrum User Group June 17, 2010

This handbook is meant to be a quick-starter guide to Agile Project Management. It is meant for the following people:

SAS Data Integration SAS Business Intelligence

Agile Overview. 30,000 perspective. Juha Salenius CSPO CSM PMI-ACP PMP SCGMIS Workshop January 23 rd, 2013

CSSE 372 Software Project Management: More Agile Project Management

Models of Software Development

Agile Software Development compliant to Safety Standards?

What is Scrum? Scrum Roles. A lean approach to software development. A simple framework. A time-tested process

Software Requirements and Specification

Understanding agile project management methods using Scrum H. Frank Cervone Purdue University Calumet, Hammond, Indiana, USA

Transcription:

14-23- 1 Agenda Scrum Kandidatprojekt datateknik - TDDD83 Vad är scrum? Hur fungerar det? Hur ska scrum användas i kursen? Aseel Berglund IDA Agile Approaches - Agile Alliance Lightweight approaches to sahsfy the customers with "early and conhnuous delivery of valuable solware" Scrum Kanban Scrum extream Programming (XP) extream Programming (XP) Other TDD (Test Driven Development) Scrum in rugby football refers to the manner of restarhng the game aler a minor infrachon. Feature Driven Development DSDM CI (ConHnuous IntegraHon) ATDD ATDD (Accenpance (Accenpance Test DTriven est DD riven evelopment) CI (Con/nuous Integra/on) Development) Kanban Manifesto for Agile So<ware Development Individuals and interac/ons over processes and tools Working so<ware over comprehensive documentahon Customer collabora/on over contract negohahon Responding to change over following a plan (hup://agilemanifesto.org, 2001) Scrum Jeff Sutherland and Ken Schwaber presented a paper describing the Scrum methodology OOPSLA '95 1

How does scrum work? Scrum Master Development Teams Product Owners SCRUM IN A NUTSHELL Scrum Master Scrum Master Small, cross- funchonal development teams Scrum master PO Product split into small, roughly eshmated, stories Rights reserved to Klean Denmark Rights reserved to KaHe Lips IteraHons - sprints ConHnuous improvement and deployment 1-4 weeks 2

Again: How does scrum work? Daily Scrum MeeHng User story Product Backlog Sprint Planning MeeHng Sprint Backlog Sprint end date and deliverable do not change Sprint review meehng? Sprint retrospechve User story )tle: As a <type of user>, I want <to perform some task=func)on> so that I can <achieve some goal/benefit/value>. User story Acceptance Test Example: User story /tle: Customer withdraws cash. As a customer, I want to withdraw cash from an ATM So that I don't have to wait in line at the bank. A clear definihon of what must be accomplished in terms of funchonality for each user story, sprint, release? 1 Epics Given creditworthy that the account is And the card is valid And the dispenser contains cash, When the customer requests the cash Then ensure the account is debited And ensure cash is dispensed And ensure the card is returned. 2 Given that the account is overdrawn And the card is valid, When the customer requests the cash Then ensure the rejechon message is displayed And ensure cash is not dispensed. Large user stories decomposed into smaller stories that fit more readily into a single iterahon. 3

14-23- 1 Sprint planning Daily Scrum MeeHng What did you do yesterday? What will you do today? What impediments stand in your way? Planning poker A consensus- based technique for eshmahng in solware development withassociates Srum task board What the teams are doing right now? A web- based collaborahon tool that organizes your projects into boards. Srum task board What the teams are doing right now? 4

14-23- 1 A graphical representahon of work lel to do versus Hme Ar fin e we ish go on ing Hm to e? Ideas Product Doing Organiza tion Team building orients energizes Team Properties of good teams AGmakonts Times Commun ication architecture decisions Product goal Organization goal Inspiring OrganizaHonal Goals Amazing Product Vision 5

Team goal goals ALer this team effort, I have <done something fulfilling for me> Journey lines Ideas Doing Team Organiza Produc tion Team goals Organizational goals Times architecture Properties of good teams Individual goals Commun ication decisions Properties of good teams Role of conflict and trust Think about teams you have been in, what did you appreciate about them? Team values and norms InnovaHon, synergy Open (posihve) conflict Trust 6

Ideas Doing Team Organiza Produc tion Properties of good teams Times architecture Commun ication decisions Time Communica tion The definihon of No more remaining work Includes coding, reviewing, teshng, documentahon, etc. Possible to ship aler each sprint Everybody understand what done means 7

14-23- 1 Architecture Work breakdown decisions Server Requirement 1 Client Requirement 2 Database Scrum team 1 Scrum team 1 Server team Requirement 3 Scrum team 2 Ideas Server Doing Client Database Database Team Story Scrum team 1 Server team Client Story Scrum team 2 Client team Story Server Organiza Produc tion Scrum team 1 Server team Scrum team 2 Client team Server Story Properties of good teams Client Story Scrum team 1 Server team Times Story Database architecture decisions Sprint retrospechve Use the sprint as input Determine the purpose upon that Choose achvihes based on the purpose Compose an agenda that focused but flexible Introduc/on Collect data Insights Ac/ons End 8

Agenda 5 min Welcome. Goal. Agenda 20 min What are we good at and " " "less good at? 20 min Which improvement ideas do " " "we have? 10 min What things should we " " "focus on? 5 min Summary and Feedback IntroducHon Collect data Insights AcHons End To improve is to change; to be perfect is to change oien - Winston Churchill Daily Scrum MeeHng TDDD83 projekt Team building Onsdag 22/1 kl 08-12 Sprint review meehng Product Backlog Sprint Planning MeeHng Sprint Backlog Sprint end date and deliverable do not change? Sprint retrospechve Ideas Doing Agenda Properties of good teams Product Organiza tion Team Mål 8:15-08:45 Egenskaper för bra team 08:45-09:00 AU jobba Hllsammans 09:15-10:00 AU jobba Hllsammans fort 10:15-12:00 Times architecture Commun ication decisions 9

1 Gör enskilt och ta med Hll lekhonen 2 Gör enskilt och ta med Hll lekhonen Rita en journey line av din karriär, med start vid vilken punkt som du vill (eler gymnasiet, start på högskola, etc) och tar den Hll nuhd. Avsikten är au lära sig om varandras kompetens, erfarenhet och kunskap Fyll i den här mening: "EIer dela teamarbete, har jag <gjort något av värde för mig> Det kan vara flera saker som du vill ha med. 3 Gör enskilt och ta med Hll lekhonen 4 Gör enskilt och ta med Hll lekhonen Tänk på två grupper/team som du har varit i, vad uppskauade om dem? skriv på en lapp Fundera över: hur du vill jobba i teamet (kommunikahon, möten, etc.) vilken ambihonsnivå du har med kursen 5 Gör Hllsammans och ta med Hll lekhonen Pdoduktmålet: visionen med produkten framhdsbild av något som ska utvecklas beskriv korvauat vad produkten ska skapa för nyua (genom au svara på varför) och för vem sylet och den övergripande karakterishken för produkten Gör deua Hllsammans i teamet Fem frågor au ställa 1. Who is going to buy the product? Who is the target customer? 2. Which customer needs will the product address? 3. Which product auributes are crihcal to sahsfy the needs selected, and therefore for the success of the product? 4. How does the product compare against exishng products, both from compehtors and the same company? What are the product s unique selling points? 5. What is the target Hmeframe and budget to develop and launch the product? 10

The Elevator Test Can you explain your product in the Hme it takes to ride up in an elevator? Moore (2006, p. 152). 11