Extreme Planning: Agile turned to the max DevDay.LK Johannes

Slides:



Advertisements
Similar presentations
Extreme Planning: Agile turned to the max Exilesoft Johannes Brodwall Exilesoft Chief
Advertisements

Extreme delivery: The real measure of progress is… Johannes Brodwall Exilesoft Chief
iRequestManager for MediMizer X3
HUMAN RESOURCES DIVISION OF FINANCE LeaveTraq Training for Employees.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
This basic tutorial will take vendors step by step through the RFQ process. The tutorial will also point out many of the exciting new.
IAgile – iNetFrame’s framework for agile development Features Get to see a working product early Development shadows evolving requirements Pair programming.
ECE44x SCRUM Overview slides adapted from Marty Stepp
Agile Project Management with Scrum
Process and tools Individuals and interactions over Following a plan Responding to change over Comprehensive documentation Working software over Contract.
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Project Management with TFS 1. What TFS offers for Project Management? Work Item tracking 2 Portfolio backlog Backlog Issue tracking Feature Product Backlog.
Scrum CS These slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
WELCOME TO SKYWARD EMPLOYEE ACCESS Step 1
SE 555 Software Requirements & Specification Requirements Management.
Managing a Project Using an Agile Approach and the PMBOK® Guide
Rainbow Sprint Plan Smidig 2012 Johannes Brodwall, Chief scientist Exilesoft.
Novus HR Application Review Process Human Resources Qualifying Applications HR Sending Applications to Department/Search CommitteeHR Sending Applications.
© 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Deeper Dive Into: User Stories.
Software Development Landscape
What is Scrum Process? Where is it used? How is it better?
Johannes Brodwall Getting your project off the ground.
Alcatel-Lucent CDC Workshop, Coaching & Knowledge Transfer Project Management.
Johannes Brodwall Getting your project off the ground.
MSF Requirements Envisioning Phase Planning Phase.
E-app Download & Agent Workspace. Laptop Presentation Training When an agent signs on e-app, if there are applications that he/she has completed and saved,
Press the F5 key to continue Project Manager is a web based Project Management Tool. All your work is done and information stored on the internet cloud.
Release and Iteration Planning September 13, 2008.
Stephen Chief Strategy Officer Telerik
GRITS Manage Orders Training Overview: Inventory and Manage Orders Functions 05/08/2014.
November 2007 LeaveTraq Training for Employees. Please Note The LeaveTraq computer screenshots used in this training will be from the LeaveTraq “Test”
Key Takeaway Points A use case is a business process; it begins with an actor, ends with the actor, and accomplishes a business task for the actor. Use.
©2011 Improving Enterprises, Inc. Epics and Agile Planning.
TROPICAL AGILE Johannes Brodwall. “How long will it take to drive to Chicago”
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
THE AGILE MENTALITY CHAPTER Topics  Why Use Agile and Scrum?  Agile Development –Manifesto for Agile Software Development  Scrum Methodology.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
Welcome to State of Michigan Time & Expense Processing Employee Expense Modification (No Advance) Tutorial Brought to you by the Office of Financial Management.
Automated Assessment Management System. The Assessment Cycle Trainee | Learner Dashboard Trainer Dashboard Employer Dashboard Verifier Dashboard Assessor.
AP-1 4. Agile Processes. AP-2 Agile Processes Focus on creating a working system Different attitude on measuring progress XP Scrum.
State of Michigan Learning Management System (LMS) for Managers
Academic Leave Academic Leave September Assumptions Training Goals Academic Leave Procedures Things to Consider Academic Leave Training.
Agile Metrics It’s Not All That Complicated. © 2011 VersionOne 2 Welcome – About your Trainer, Katia Sullivan VersionOne Product Trainer and Agile Coach.
Hatrak Scheduler UsOn Line Demo HATRAK SCHEDLER.
Sprint Plans and Burndown Charts David Millard | davidmillard.org.
Johannes Brodwall Chief Scientist Smidig arkitektur.
SCRUM.
WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ CA Agile Vision Product Manager Michael Lester.
Step 1 Lead Notifications Dear Partner, New leads have been assigned to your organization based on customer preference and are available for you.
Agile CRM Applying the Scrum Methodology for Deployment Neil Benson.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum and TargetProcess
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Scrum Management
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
By: By: Agile Scrum Master Online Training.
Chapter 3: The Project Management Process Groups: A Case Study
Scrum MODULE 3 – Part 3.
How to Successfully Implement an Agile Project
AmeriCorps Member Tutorial – OnCorps Reports 2.0, Standard Reports
Health-e Claims July 2007.
Introduction If you have got a call for an Agile testing interview, then congratulations are in order. You may be feeling nervous, but it sure to be felt.
Introduction to Agile Blue Ocean Workshops.
Software Development In Agile
Software Development In Agile
Presentation transcript:

Extreme Planning: Agile turned to the max DevDay.LK Johannes

This talk is about

What’s this thing we are building?

Use that understanding to plan the work

A simple way to measure progress

(that works just as poorly, but is simpler)

After this talk

Uncover what needs to be done

Forecast from actual progress

Plan ourself out of the rush

But first

Where does the rush come from?

Part I

Yesterday’s weather

“How long will it take to drive to Chicago”

Kandy

t = s/v

After 1 hours, we have only got to Mahara…

v estimate > v measured

Product backlog

8 8

8 weeks?

8 sprints?

5 stories planned

(or 5 stories * 3-8 story points = 25 story points)

5 stories planned

4 stories delivered

6 stories delivered

7 weeks

How many hours?

Cost = (burn rate) * (time) = (team cost) * (backlog) / velocity

Architect

The worst way to answer: To estimate hours per task

Actual hours = Σ estimated hours per task * “load factor” * “management overhead” * fudge factor

Actual hours = Σ estimated hours per task * whatever

Part II

Creating the backlog

Vision Usage flow Product backlog

Vision, stakeholder

For some stakeholder Who wants achieve some goal The ??? system Is a type of application Which lets them perform some actions. Unlike most relevant alternative Our product has some advantage

For company employees Who wants to take leave from work The Leave-IT system Is a responsive web application Which lets them register leave applications and get them approved Unlike sending s Our product lets them keep track of leave days available and team leaves

Employee Team lead PMOHR Leave-IT HRDB SSO

Usage flow

1.HR admin logs in via SSO (same for the other stakeholders) 2.HR admin navigates to Leave-IT 3.HR admin allocates leave quotas based on information in HR database 4.HR admin builds company calendar 5.HR admin adjusts the leave quota for an individual user in HR system 6.HR admin assigns leave approvers from uses in HR system 7.Employee views their available leave 8.Employee submits leave request 9.Leave-IT notifies Team leader of a new pending leave request via 10.Team leader views pending leave applications 11.Team leader checks the other leaves in the same time period 12.Team leader approves leave 13.Leave-IT notifies Employee of an update of his leave request via 14.Employee checks status of own leave application 15.Employee cancels own leave 16.PMO views the teams' leave calendar, plans and history 17.PMO may cancel leave if necessary

Minimum interesting demo

1.HR admin logs in via SSO (same for the other stakeholders) 2.HR admin navigates to Leave-IT 3.HR admin allocates leave quotas based on information in HR database 4.HR admin builds company calendar 5.HR admin adjusts the leave quota for an individual user in HR system 6.HR admin assigns leave approvers from uses in HR system 7.Employee views their available leave 8.Employee submits leave request 9.Leave-IT notifies Team leader of a new pending leave request via 10.Team leader views pending leave applications 11.Team leader checks the other leaves in the same time period 12.Team leader approves leave 13.Leave-IT notifies Employee of an update of his leave request via 14.Employee checks status of own leave application 15.Employee cancels own leave 16.PMO views the teams' leave calendar, plans and history 17.PMO may cancel leave if necessary

Product backlog

1.Experimental submit leave 2.Experimental show leave status 3.Simplified layout and style 4.Simplified approve leave 5.Simplified view leave request 6.Simplified submit leave

Experimental X Simplified X Basic X Complete X Polished X

Demo/deploy/automate Styling Testing Learning

Step 4 Step 3 Step 2

Experimental X Simplified X Basic X Complete X Polished X

Release/ deployment Architecture through spike Technology study

EstimatePlan

Part III

Planning the sprint

Planning the demo

(content)

Experimental submit leave request 1.Go to the front page 2.See that there is a dropdown with possible users and approvers 3.Select a user, approver, start date, end date, reason 4.See that the number of days is updated 5.Click submit 6.See that the data is in the database 7.Submit a request with no start or end date 8.See that there is an error message 9.See that the data is not in the database

Log in using Exilesoft SSO (foreign user story from SSO) 1.Open a new web browser and go to the application 2.Verify that the user is not logged in 3.Click login 4.The user is sent to Exilesoft SSO 5.Verify that the username is correct when the user is returned to application TODO SSO must support cross-domain authentication

Log in using Exilesoft SSO (foreign user story from SSO) 1.Delete any existing permission from 2.Open a new web browser and go to the application 3.If you are logged in, click log out 4.Click login 5.The user is sent to Gmail to authenticate 6.Deny the authentication request 7.Verify that the login button is still displayed 8.Click login again 9.Allow the authentication request in Gmail 10.Verify that the users address is displayed 11.Click log out 12.Verify that user address is no longer displayed

Planning the demo

(time)

Planning the demo

(practice)

Log in using Exilesoft SSO (foreign user story from SSO) 1.Delete any existing permission from 2.Open a new web browser and go to the application 3.If you are logged in, click log out 4.Click login 5.The user is sent to Gmail to autenticate 6.Deny the authentication request 7.Verify that the login button is still displayed 8.Click login again 9.Allow the authentication request in Gmail 10.Verify that the users address is displayed 11.Click log out 12.Verify that user address is no longer displayed

What are we doing? When are we done?

Cost = (burn rate) * (time) = (team cost) * (backlog) / velocity

Create backlog from usage flow

Track stories per week Forecast Actual

Plan features with demo script

Thank you

Context –“We get a tender with epics and need to give a price” (Janini, Virtusa) –We have a team that is “confused” – beginning or halfway through Get a team together and discuss the who, why, what (actions) and alternatives (vision statement) Use actions to start the discussion of the usage flow (a narrative that starts with the first interaction with the (sub)system and ends when the business value is produced) Create the product backlog from the usage flow. I like the items on the product backlog to be man- week sized. Each action from the usage flow goes into the product backlog. In addition, the product backlog should contain activities for layout, deployment, specific testing etc. –Separate different iterations on the same increment in time to accumulate feedback –Prioritize the items for the first internal demo, first external demo and first trial deployment –Simplified user stories can be used to detach teams This gives a list which length predicts the number of weeks. Weeks = # Items / number of item producers. Hours = Weeks * Burn rate Tracking –As project proceeds, track actual progress (count of items per week) versus forecasted progress. Also track changes in total scope. This will adjust the forecasted times and costs. –Demonstrate with the customer whenever you can. This will determine if the quality matches their expectations –Deviation in progress, changes in scope or missed expectations mean you should discuss contract with customer or suffer consequences Focus through demo planning –In scrum planning, when you know the scope, come up with a screenplay script for the demonstration. Get someone brave to give a mock demonstration during the planning. => Focus on the outcomes –Use the demo focus to help the team break down technical dependencies –Practice the demo towards the end of the sprint –Give a demo like you mean it, but don’t lie (unless you want to delude the value of the feedback)

Planning – man-week sized items –Gather “everyone” to discuss => usage flow –Usage flow actions x revisits (experimental, simplified, basic, complete, polished), technical items (layout), releases => product backlog (releases planned in time) Revisits with different expectations (experimental, simplified, basic, complete, polished) – also used to avoid deps Technical items with visible results Releases –Product backlog => time and cost (t = s/v) Tracking every week –Actual production, changes in scope –Demonstrations with customers => expectations –Progress, scope, expectation/insufficient done-ness => risk Accelerating with demo –Practice mock demo during planning Example project: Planning Monday, Demo rehearsal Friday morning, Demo Monday morning –Use demo driven work to focus on feature slices (avoid deps) –Demonstrate with externals to get feedback

Planning – man-week sized items –Gather “everyone” to discuss => usage flow –Usage flow => product backlog –Product backlog => time and cost (t = s/v) Tracking every week –Actual production, changes in scope –Demonstrations with customers => expectations –Progress, scope, expectation/insufficient done-ness => risk Accelerating with demo –Practice mock demo during planning –Use demo driven work to focus on feature slices (avoid deps) –Demonstrate with externals to get feedback

TODO Need better example project (Architecture – don’t play) Team-mbedded product management