Business Analysis - Requirements

Tutorials

MM Innovation Thinking: Evolve and Expand Your Capabilities

Jennifer Bonine, tap|QA, Inc.

Mon, 11/09/2015 - 1:00pm

Innovation is a word frequently tossed around in organizations today. The standard cliché is “Do more with less.” People and teams want to be innovative but often struggle with how to define, prioritize, implement, and track their innovation efforts. Jennifer Bonine shares the Innovation Types model to give you new tools to evolve and expand your innovation capabilities. Find out if your innovation ideas and efforts match your team and company goals. Learn how to classify your innovation and improvement efforts as core (to the business) or context (essential but non-revenue generating). With this data, you can better decide how much of your effort should be spent on core versus context activities. Take away new tools for classifying innovation and mapping your activities and your team’s priorities to their importance and value. With Jennifer’s guidance you’ll evolve and expand your innovation capabilities on the spot.

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.

TK Mobile App Usability and UX for Developers and Testers

Philip Lew, XBOSoft

Tue, 11/10/2015 - 1:00pm

Many enterprises today are migrating to mobile while new organizations are adopting a mobile-first or mobile-only strategy. Because of the special characteristics of the mobile platform and its user base, usability and the user experience (UX) take on an increased emphasis, although there are currently no formal models describing UX. With SaaS-based business models, where users can pay by the month and switch applications in a heartbeat, UX becomes paramount. Phil Lew explains the definitions of usability and user experience, describes the connections between them, and explores evaluation methods you can use as the first step toward improving UX on the mobile platform. To build a deeper understanding of how to improve your own app’s UX, Phil gives examples to illustrate the good, the bad, and the ugly of mobile UX. Discover key principles for design and evaluation of usability. Develop a methodology for continuous improvement of your users’ experience.

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.

AW3 Your Agile Prioritization Process Is Probably Wrong

Tom Gimpel, SofterWare, Inc

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

Of course we know what customers want, right? Product owners have the roadmap. Sales teams know what sells. Support talks to customers every day. So if we really know what our customers want, why is 65 percent of all software functionality rarely or never used? Why aren’t our customers delighted with the products we ship? Stop guessing what customers want and start delivering it! Tom Gimpel discusses the challenges of feature prioritization and determining what your clients really want and what they really need—and why they’re not the same thing. Learn how you can employ the KANO prioritization model to delight your customers by giving them functionality they value without the fluff they won’t use. Learn what’s wrong with most feedback surveys and build your delivery process to maximize customer satisfaction. Take away valuable tools for prioritization including an Excel-based scoring model that actually chooses the “best” possible combination of features that you can ship.

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.

AT13 Applying Lean Startup Principles to Agile Projects

Michael Hall, Improving Enterprises

Thu, 11/12/2015 - 3:00pm

Warning! You can still build the wrong product using agile. In Eric Ries’ book The Lean Startup, he poses the question: What if we found ourselves building something that nobody wanted? In that case, what would it matter if we did it on time and on budget? We often assume the Product Owner is smart enough to define the right product. But what if we are wrong? Michael Hall shares lean startup principles and how they can be applied to ensure that the product we are building is righteous. Learn new agile concepts such as hypothesis-driven project vision, knowledge broker personas, learning maps, minimum learning product, experiment backlogs, experiment test iterations, validated learning, and pivot/persevere decisions. Case studies and Michael’s first-hand product experience emphasize the learning points. New and mature agilistas alike will leave the session armed with Lean Startup agile techniques that can be applied immediately on their agile projects.