Week Assignment Software Processes - Agile/Scrum

Size: px

Start display at page:

Download "Week Assignment Software Processes - Agile/Scrum"

Richard Perry
6 years ago
Views:

1 Week Assignment Software Processes - Agile/Scrum Hans-Petter Halvorsen

2 All Documents, Code, etc. should be uploaded to Visual Studio Team Services (VSTS) Week Assignment 1. Create/Update Product Backlog Items and Tasks in VSTS based on SDP and SRD documents Create/Update the Product Backlog Create/Update the Sprint Backlog 2. Perform a Daily Scrum Meeting 3. Finishing the Alpha Release (Deadline Next Week) 4. Quiz. Extended and Important Quiz (35 Questions) (Next Week: Sprint Review & Planning) See Next Slides for more details...

3 Introduction Software Processes - Agile/Scrum Hans-Petter Halvorsen

4 Typical Job Ad Many Job Ads today ask for Agile/Scrum skills! - And skills within Web, ASP.NET, C#, HTML5, SQL and Database Systems Agile methods and especially Scrum have become very popular these days!!

5 More Job Adds

6 Traditional Plan-driven vs. Agile Software Development Processes Traditional/Plan-driven "Cannot" go to next phase before previous phase is finished Waterfall V-model Spiral... Agile Scrum Lean More flexible, Iterative and Incremental Approach exreme Programming (XP) Kanban RUP TDD FDD Rational Unified Process... We will mainly focusing on Waterfall and Scrum in Class. But you should read and get an overview about all these Software Development Processes in the Textbook!

7 The Waterfall Model Planning to create a new Software Requirement Finished A Sequential Process Not Finished? -Go back and Fixit! Design Not Finished? -Go back and Fixit! Finished Implementation Not Finished? -Go back and Fixit! Finished Testing Finished You cannot go to next phase before finished the previous phase Not Finished? -Go back and Fixit! Deployment Maintenance Software Finished

8 Customer Involvement Agile (Norsk: Smidig utvikling) Pair Programming Test Driven Development (TDD) Incremental Work in Iterations Less Documentation. Only what's necessary Continously Integrate Changes Refactoring Communication Working Software at All Times

9 Waterfall vs. Agile Value Delivery Risk of Failure Waterfall Agile Result Result Time Time Iterations

10 Agile/Scrum Development Daily Scrum Meetings Sprint Reviews & Planning 2-4 weeks 1-12 months 24 hours Days Working Software at all times. Testing every day Weeks Iterations/Sprints Finished Months

11 Which Process are we using in the Project? We will use different Development Processes throughout the project The goal is to learn about different methods and test out some of them in real-life. You should be able to know the main features and be able to choose and apply a proper method for a specific project We should know advantages and disadvantages of different methods

12 Which Process are we using in the Project? Planning Requirements Analysis Implementation Design Testing Deployment & Maintenance We are using: Waterfall Waterfall Scrum Waterfall + Scrum mix Start E.g., UML are not in focus in Scrum We create different documents We create Product Backlog and use Taskboard Start

13 Introduction to Scrum Hans-Petter Halvorsen, M.Sc.

14 Video: Scrum in 2 minutes Scrum in 2 Minutes: (Olav viser videoen på ActivBoard)

15 Scrum Members: Scrum Overview Product Owner Sprint Backlog Product Backlog Stakeholders Scrum Process: Sprint Planning Meeting Scrum Master Development Team 3-9 persons Daily Scrum Meetings Max 15 min. Sprint Review

We will practice these meetings during the course Scrum Meetings Product Backlog Sprint Planning Meeting Sprint Start Sprint Backlog The work to be performed in the Sprint is planned at the Sprint

16 We will practice these meetings during the course Scrum Meetings Product Backlog Sprint Planning Meeting Sprint Start Sprint Backlog The work to be performed in the Sprint is planned at the Sprint Planning Meeting. This plan is created by the collaborative work of the entire Scrum Team. Daily Scrum Meeting 24hours Synchronize activities and create a plan for the next 24 hours Short Status Meeting Sprint 2-4 Weeks After the Sprint is finished, the Team demonstrate what they have done in the Sprint Sprint Review Meeting Sprint Retrospective Meeting The Team reflects on its own process and learn from that. What was good? What was bad? Sprint Finished

The Official Scrum Guide http://www.scrumguides.

html Make sure you read this (at home) This guide

17 The Official Scrum Guide Make sure you read this (at home) This guide gives a very good overview of Scrum! The Scrum Guide is available in many languages

19 VSTS: Product Backlog Items and Tasks Create/Update your Product Backlog Items (PBI) and Tasks in VSTS Use the SRD document as a foundation for creating the Product Backlog Items and Tasks Create/Update your Spring Backlog for the Alpha release/iteration Make sure to include Responsible Person and Estimated Hours See Next Slides for more details...

Visual Studio Team Services (VSTS) Start using Scrum within Visual Studio Team Services (VSTS): Create/Update Product Backlog in VSTS Create the different Iterations for the entire Project with Start

20 Visual Studio Team Services (VSTS) Start using Scrum within Visual Studio Team Services (VSTS): Create/Update Product Backlog in VSTS Create the different Iterations for the entire Project with Start and End Dates Start Create Sprint Backlog for the Next Iteration (Beta Release) in VSTS Start using the Taskboard in VSTS Cont. Next Week Give access to and send the Project URL on to the supervisors See Next Slides for more details...

21 VSTS/Product Backlog Create/Update Product Backlog Items and Tasks in VSTS based on SDP and SRD documents SDP Existing Documents Software Development Plan Gantt, etc. VSTS Resources, Deadlines, Team's capacity, etc. Sprint Start/Stop Dates, etc. WHAT HOW SRS Software Requirements Specifications SDD SRD Software Requirements & Design Software Design Document Product Backlog Items Tasks HOW WHAT

22 Introduction Product Backlog, Sprint Backlog Hans-Petter Halvorsen, M.Sc.

23 Product Backlog Software Requirements and Design (SRD) Used by the Customer, Managers, etc. Product Backlog PBI Used by the Scrum Team Create all Requirements from SRD into Backlog Items (in prioritized order). Then break the Backlog Items into Manageable Tasks

24 The Product Backlog in VSTS

25 Product Backlog Example PBI...

26 Just Drag Items from the Product Backlog to the Sprint Backlog The Sprint Backlog in VSTS

27 Create Tasks in VSTS Break down Product/Sprint Backlog Items into workable Tasks Max 8 hours

28 Task Board Drag and Drop Tasks 55

29 Sprint Task Board Example To Do In Progress Done Create Web Interface HPH 4h OD Create Database 7h Create UML NOS 3h Create GUI HPH 8h Task Name Estimated Hours Responsible Person GUI Mockup OD 6h The Taskboard has to be updated on a daily basis

30 Remaining Work (Hours) Burndown Chart Sprint Start Actual Burndown Ideal Burndown Tracking the Progress Days Important Project Management Tool in Scrum Sprint Finished

32 Daily Scrum Meeting Hans-Petter Halvorsen, M.Sc.

33 Video: Microsoft Daily Scrum Meeting Microsoft Daily Scrum Meeting: (Olav viser videoen på ActivBoard)

34 Product Backlog Sprint Backlog Taskboard Daily Scrum Meeting

35 3 Questions: Daily Scrum Meeting 1. What did you do yesterday (since last meeting)? 2. What shall you do today (until the next meeting)? 3. Any Problems? Purpose with the Daily Scrum Meeting: - Synchronize activities and create a plan for next 24 hours. - Track Progress

36 Video: Daily Scrum Meeting Bad Example Daily Scrum Meeting Bad vs Good Example: (Olav viser videoen på ActivBoard) (we stop at 3:30 in class - watch the rest at home)

Daily Scrum Meeting - Summary Max 15 min. Same Time and Place every day Don't be late No phones, no checking E-mails, etc. (No distractions) Each answer 3 Questions (Don't go into details!). No others can talk while answering the questions.

37 Daily Scrum Meeting - Summary Max 15 min. Same Time and Place every day Don't be late No phones, no checking s, etc. (No distractions) Each answer 3 Questions (Don't go into details!). No others can talk while answering the questions. Update your Tasks and the Electronic Task Board before the meeting (if sticky notes, you can update the Task Board while answering the 3 questions) Stand up (don't sit down) during the whole meeting Show the Burn-down Chart at the end of the meeting

38 Daily Scrum Meeting Prepare for your first Daily Scrum Meeting We divide the whiteboards in 4 parts where you draw a simple Taskboard (3 columns: To Do, In Progress, Finished ) Create a set of remaining Tasks for the Alpha iteration on yellow Sticky Notes and place them on your Taskboard. Prepare the Answers for the 3 Questions ( Have done?, Shall do?, Problems? ) Perform your first Daily Scrum Meeting Each in the Team should answer the 3 Questions Move Tasks on the Task Board ( To Do -> In Progress -> Finished ) Try also to create a Parking lot if necessary Try also to draw the Burn down Chart

39 Task Board Sprint: Finishing Alpha Release To Do In Progress Done Oppdater SRD med UML HPH 2h Søknadsskjema for webside HPH 0.5h Oppdater ER modell OD 1h Legg inn PBI/Tasks for Databaseutvikling NOS 1h Oppdater folderstruktur i VSTS NOS 0.5h Sjekker inn all dokumenter i VSTS OD 0.5h Installer FTP program for opplasting til Web Server NOS 0.5h osv. osv. osv. Hver person på gruppa bør lage 3-10 gule lapper

Answers/ Keywords down on a piece of paper) Use your Whiteboard

No Discussions or Problem Solving in the Meeting.

40 Daily Scrum Meeting Max 15 Minutes! Select a Scrum Master Prepare for the 3 Questions (Write the Answers/ Keywords down on a piece of paper) Use your Whiteboard Taskboard and have your first Daily Scrum Meeting with your Team. No Discussions or Problem Solving in the Meeting. Use the sidebar/parking lot to stay within the 15-minute time box (i.e., Write it down and take it right after the meeting)

41 Regular Daily Scrum Meetings Your Team should have regular Daily Scrum Meetings during your Project We only work 33% so obviously you cannot have it every day but you should at least have it once a week It is the Scrum Master in your Team that is responsible to facilitate these meetings

43 Finishing the Alpha Release If you have done the following when the Alpha release is finished, you are on track with your Project: 1. Documents: The following Documents should be finished : Software Development Plan (SDP) Product Description, Team Description and Project Organization, Gantt Chart, Tools and Templates, etc. Software Requirements and Design (SRD) System overview, System and User Requirements, Functional and Non-Functional Requirements, GUI Sketches, ER diagram, UML Diagrams 2. Software/Programming: Tables Implemented in SQL Server Generated from ERwin Script You know how to Communicate with your SQL Server Database from C# Code (You have made some examples) You have made some simple ASP.NET Example Applications ( Hello World App, etc.) You have created Classes and Methods (according to the UML diagrams) - not the contents in the Methods, just the Names/declarations 3. Visual Studio Team Services: Folder structure has been made + Iterations Product Backlog has been made (PBI + Tasks) All Documents and Diagrams have been uploaded/checked-in Code Examples/Prototypes have been uploaded/checked-in 4. Project Web Page (-> We shall do this next Week) A simple HTML Web Page with an Introduction (Text and Figure) + Links to SDP and SRD (PDF)

44 Requirements/Design Alpha Plans made and approved Beta RC Foundation finished, building structure started A proof that you can do it, PoC (Proof of Concept) RTM Building structure finished, Inside work on track Furniture, Flowers and small adjustments missing Ready for Sale or Move in

45 Preparation for Next Week: Prepare for Web Site Next week we will create a Web Site (HTML, CSS) that introduces the product you are creating, including documents you have created (SDP, SRD,...) This is an individual activity, meaning all team members should create such a web site. You need to know basic HTML. A good source is: Recommended HTML Editor: Visual Studio Code (or you can use Visual Studio, but VS is not well suited for HTML pages) The best web site within each group should then be selected and used further in the project. We will use the available Web Servers at the university. The Web address (URL) will be like this: or Resources:

46 Simple Web Page in Visual Studio Code

because the Web Server we are using at school don't support it).

47 Web Site Example Create a similar Web Site for your Product Presentation (Figures and Text) of your Software Product Note! We should use only HTML (not ASP.NET! because the Web Server we are using at school don't support it). In addition you may use JavaScript, CSS, PHP Documents available for download (Hyperlinks) Note! Always use PDF Files!!!

48 Web Development in your Project 1 HTML ASP.NET 2 Det er denne dere skal lage neste uke Eksempel på innhold: Tittel Figurer og kort beskrivelse av produktet deres Linker til dokumenter (PDF) som SDP, SRD (flere dokumenter kommer senere) Link til setup, e.l. (Kommer senere) m.m. Commercial Web Page with information about your Product, you can download setup files, documents, etc. vs. Dette er produktet deres som dere skal lage ihht SRD Your web-based Product -> Web Application

49 Illustrative Example 1 2 Product Information Web Site vs. Product Web Site

Hans-Petter Halvorsen University of Southeast Norway www.usn.

50 Hans-Petter Halvorsen University of Southeast Norway Web:

The Software Development Process (SDLC)

http://home.hit.no/~hansha/?page=software_development O. Widder. (2013). geek&poke. Available: http://geek-and-poke.com The Software Development Process (SDLC) Hans-Petter Halvorsen IT System B. Lund.