Requirements

Tutorials

ME A Product Ownership Practicum for ScrumMasters and Product Owners NEW

Bob Galen, Velocity Partners

Mon, 11/09/2015 - 8:30am

You’ve just been selected by your boss for the Product Owner role … or you’re a newly minted ScrumMaster trying to figure out how it all works … or you’re an experienced Product Owner who is struggling to find balance between your stakeholders, customers, and team … or you’ve just received your CSPO certification but have no experience being a REAL Product Owner. Fear not! Join Product Owner coach and author Bob Galen in this fast-paced, crash course in how to ROCK your new role. Explore the dynamics of user stories, product backlogs, valuation and prioritization, establishing minimal marketable deliverables, and how to deliver high-impact sprint reviews. Bob then raises the bar to talk about product ownership at scale, how to build quality into your products, and how to effectively communicate and negotiate within your organization. Leave this tutorial with the ideas, skills, and techniques to become the Product Owner your boss wants you to be.

TB Requirements Engineering: A Hands-On Practicum SOLD OUT NEW

Erik van Veenendaal, Improve IT Services BV

Tue, 11/10/2015 - 8:30am

Identifying, documenting, and communicating requirements are key to all successful IT projects. Common problems in requirements engineering are How do we discover the real requirements?, How do we document requirements?, and How do user stories, use cases, and epics fit into requirements? Erik van Veenendaal answers these questions and more while helping you improve your skills in requirements engineering for both traditional and agile projects. With practical case studies and hands-on exercises, Erik illustrates requirements issues and solutions. Practice specifying and evaluating traditional requirements and user stories while learning how to gather information through varied elicitation techniques. Explore the advantages and disadvantages of each technique. Learn a rule set for determining how much documentation you need for “good enough” requirements. Explore requirements review techniques—walkthroughs and inspections—to determine what will work best for you. Create a set of Golden Rules for requirements engineering that your project can use.

Concurrent Sessions

AW2 Data-Driven Software Engineering for Agile Teams

Viktor Veis, Microsoft

Wed, 11/11/2015 - 11:30am

Remember the old days when software engineering teams used to tune software until it passed quality gates, gave golden bits to marketing, and finally threw a big release party? The world was simple, and writing code that worked according to a specification was enough to be a star developer. Viktor Veis says that world has changed. Software now often dials back home to record information about its usage and health. This telemetry flows back to engineering teams who are accountable for making sense out of this data. This is a fundamental shift in the software engineer role. Teams who can leverage data-driven engineering will delight customers by learning more about customers than they know about themselves. Teams who ignore data-driven engineering will continue based on assumptions and eventually lose competitive nerve. Join Viktor to learn how to start data-driven engineering today. Discover a practical approach that sometimes deviates from classical data science but is easy to learn and apply.

AW7 Product Backlog Refinement: Grooming Your User Stories

Becky Moshenek, ANCILE Solutions

Wed, 11/11/2015 - 1:30pm

The Scrum Guide describes Product Backlog Refinement as “the act of adding detail, estimates, and order to items in the Product Backlog.” New and even experienced agile teams often underestimate the importance of well-groomed stories and find the process of reviewing numerous stories, breaking them down, and estimating the work chaotic and cumbersome. As this happens, teams push problems downstream into sprint planning meetings—or worse, into the sprint. Becky Moshenek shares how, working with the Product Owner, they create stories for backlog items to be reviewed. The stories include a link to the actual item, tasks outlining how and what to review, and a deadline for a future refinement meeting. These become refinement stories that are assigned to team members and brought into a sprint for an allotted ten percent of their time. Coordinating the team’s effort around backlog refinement in this way has cut meeting times, increased team involvement, produced more polished items, and made for a happier team.