Managing Requirements and User Expectations in Agile ProjectsSteven BorgCo-Founder and StrategistNorthwest CadenceSteven.Borg@nwcadence.com

DEV-B326

AgendaNudityCircle of LoveUnintended HumorSimplicityForgivenessPillow Talk

Circle of LoveReducing cycle time is about far more than developing in sprints

reduce time to feedback

DefineIdeation

DevelopIdea to working software

OperateWorking software to business outcomes

Requirements backlog

Operations backlog

MonitorImplement

SHORTENEDCYCLE TIMES

Team

MeasureValidated learning

Unintended HumorRight sizing requirements

As an executive, I want to expand to new markets so that we can improve overall profitability and lower risk.

To do Doing Done

To do (3) Doing (4) Ready (3) In Prod

Executive/Vision levelIdeas are refined, prioritized, budgeted, resourced, tracked through realization

Management/Epic levelEpics are defined, decomposed into stories, prioritized, and pulled by teams

To do (3)

Design (2)

Dev (3) Test (2) Done

Teams/User Story levelStories are implemented; teams self-organize within a common cadence

To do (6) Doing (6) Done

requirements at different levels are different…

…but relatedExecutive/Vision levelSets the priority for ideas

Management/Epic levelDetermines the breakdown and ordering needed to deliver ideasSets the priority for epics

Teams/User Story levelDetermines the breakdown and ordering needed to deliver epics

team requirementsUser stories are an excellent choiceAs a <role>, I want <activity> so that <value>Card, confirmation and conversation

As a TechEd attendee, I want to quickly provide session ratings so that I can provide effective feedback and improve future events.

Acceptance Criteria:1) Identify URL in < 10

seconds2) Persist logins between

browser sessions3) Search for session by

number, title or speaker4) Provide feedback in < 1

minutes

management requirementsEpics/Features in user story form are often an excellent choiceAs a <role>, I want <activity> so that <value> still works at this level, but generally more vague

Card, confirmation and conversationOften additional data is required since conversations at this level can be more difficult to schedule

As a TechEd planner, I want a session and speaker rating system so that both good and poor topics and speakers can be identified to improve future events.

Acceptance Criteria:1) System is easy to use2) Speakers can view all

session scores, not only their own

3) Attendees are able to easily rate sessions and speakers

executive requirementsPortfolio management Investment fundingChange managementGovernance

Backlog metaphor often breaks downInvestment generally spans several efforts

Requirements tend to be provide more analysis, justification and risk mitigation

A3 problem solving

Team Foundation Server

To do Doing Done

To do (3) Doing (4) Ready (3) In Prod

Executive/Vision level“Backlog” items potentially persist for 6 months to several years

Management/Epic levelBacklog items look ahead 2-6 months

To do (3)

Design (2)

Dev (3) Test (2) Done

Teams/User Story levelBacklog completed in 2-4 weeks

To do (6) Doing (6) Done

requirement backlogs decay at different times

To do Doing Done

To do (3) Doing (4) Ready (3) In Prod

Definition of doneCriteria for final acceptanceThe what, not the howMore than functional: -ilities, standards

Ready stateA definition of done for to-do columnWhat’s needed to get startedNot necessarily all info needed to finishTo do

(3)Design

(2)Dev (3) Test (2) Done

Let teams figure out their how

To do (6) Doing (6) Done

requirement responsibility is distributed

Management level defines ready

Exec level defines done

Management level defines done

Team level defines ready

InteGREAT

full featured support for requirements

requirement hierarchy support

questions to help elicit requirements

visual traceability + matrix

SimplicityComplex and expensive solutions aren’t always better

ForgivenessAct fast, get feedback.

feedback fuels agileProduct OwnerPowerPoint Storyboarding

CustomersUser VoiceFeedback Client

PowerPoint Storyboards

User Voice

Questions

…before the final demo

Pillow TalkUse the Feedback Client!

Feedback Client

msdn

Resources for Developers

http://microsoft.com/msdn

Learning

Microsoft Certification & Training Resources

www.microsoft.com/learning

TechNet

Resources

Sessions on Demand

http://channel9.msdn.com/Events/TechEd

Resources for IT Professionals

http://microsoft.com/technet

Complete an evaluation on CommNet and enter to win!

MS tag

Scan the Tagto evaluate this session now on myTechEd Mobile

© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.