Better Software West 2018 - Business Analyst - Requirements

Have you ever been in the same room with co-workers and sent them a Slack or text message instead of having a live conversation? Many people are starting to prefer virtual or instant chat messaging to live conversations, but live communication can get better results at work—and with your customers. As technology professionals, we often focus more on technical skills and ignore the important communication skills. Join Jennifer Bonine to see how to make the most of—and get the best results from—your live conversations. Jennifer shares a toolkit to help you assess your core communication...

Do you know how your work is aligned to tactical and strategic goals? Success is rooted in a productive and cohesive team-centered culture. When culture and execution are misaligned, failure is almost certain. Everyone on and around the team must understand their role in defining, delivering, and growing value. It sounds easy, but the discipline can be tough, which leads to disappointments and unwelcome surprises. Nabila Safdar focuses on curating transparent expectations by the following six core practices. First, foster candor and respect. This leads to unity. Second, have fresh...

So, your company wants to be innovative. Are you comfortable with failure? The word failure is littered with negative connotations. Elon Musk financed three failed SpaceX rocket launches. Edison designed more than 2,000 light bulbs that did not work. The Wright brothers crashed dozens of planes and gliders before one took off. And the Americas were discovered through failed circumnavigation. Some failed small and learned. And some failed big but survived and thrived. The lesson is that organizations must embrace failure to accelerate innovation. Join Stefana Saxton to learn how to...

Defining, understanding, and agreeing on the scope of work to be done is often an area of discomfort for product managers, business analysts, developers, and quality assurance experts alike. The origin of many items living in our defect tracking systems can be traced to the difficulties encountered while performing these initial requirements activities. Ken Pugh introduces behavior-driven development (BDD), also known as acceptance test-driven development (ATDD), and explains how it works in creating detailed requirements. He outlines the different roles that team members play in the...

Most agile practitioners first learn agile by reading a book, attending a class, or attending local meetings. But learning lean and agile concepts works best when we're able to put some concrete examples and practice behind the concepts. By adding a set of games and exercises that teach and reinforce lean and agile concepts to our toolboxes, change agents can provide some practical basis for conversations both inside and outside their organizations. In this talk join experienced agile coach Bill DeVoe, as he shares two of his “go to” games. First, up will be The Name Game, a game that...

"Move fast and break things” tells quite a story of the relationship between speed and agile. Speed has been a driver in our industry before it was even an industry. Books promise that certain frameworks can deliver twice as much in half the time, yet teams still struggle delivering what's expected of them. This session describes a six-month case study of a multi-team transformation. The orders were to make the teams deliver faster, but they were consistently missing deadlines. Frustration was on the rise. Only after taking the time to understand what they meant by "faster" could the teams...

"Efficiency is doing things right; effectiveness is doing the right things." This quote from Peter Drucker identifies why even the most productive agile teams may not always deliver the most successful business solutions. The agile team depends on the product owner to correctly identify the business requirements with the highest values, to clearly describe each feature at the right level of granularity, to provide the necessary supporting documentation, and to continuously adapt the product backlog to meet the emerging needs of the organization. Otherwise, the team could be measuring its...

The problem with many agile teams is that they simply never become a team. This often manifests itself as team members feeling unsafe or not quite trusting each other. This workshop will show you how the same techniques improv theater troupes use to improve collaboration, creativity, and communication can be used to help agile teams, too. The three-minute improv warm-up games Wayde Stallmann will lead you through in this session—including improv's famous "yes, and" technique—will help you learn to establish trust, improve collaboration, and learn how to provide a safe environment for your...

Scrum surfaced in 1993. So, the role of a Product Owner has existed for 20+ years. Surely the whole idea is well understood by now. Right? And the role is a simple one. There is a single product owner per product team or teams. Defining and accepting the work to meet the clients’ goals. Always mucking around the backlog. Again, simple and clear. Right? Well, in my coaching travels and observations it’s not that simple. I still see literally tens of organizations and hundreds of teams that struggle with the notion of product ownership. So, let’s go over it...