business analysis

Articles

The Effect of Time on Value in Your Agile Projects

Using effort estimates as the only criteria for deciding whether work is undertaken could be leaving money on the table. Considering value—in particular, the effect of time on value, as in whether there is a cost of delay—makes for more intelligent conversations and better decisions.

Allan Kelly's picture Allan Kelly
Implementing Agile Approaches in the Public Sector

In the public sector, a change in standard processes and procedures requires significant effort and, often, approval from external vendors and elected officials as well as internal stakeholders. To get buy-in to become agile, you have to utilize all Scrum tools at your disposal to show the value of the proposed agile process.

Khurram Shahzad's picture Khurram Shahzad
Estimating Business Value in the Shark Tank

You can use analytical methods to assign business value to a user story, of course, but another way is simple estimation. Allan Kelly describes an estimation exercise that combines the Scrum tool of planning poker with a TV show format to add some fun. You end up with enlightening conversation and revealed requirements.

Allan Kelly's picture Allan Kelly
Business and Development: Working Together to Build Better Products

Business stakeholders and DevOps teams both have to take an active approach to app development, but neither faction should have to change practices and processes in order to get their needs across. Investing the time to establish communication between these teams will drive delivery of the applications customers demand.

Renato Quedas's picture Renato Quedas

Better Software Magazine Articles

Six Ways to Use Business Analyst Superpowers in Agile

There are those agilists who believe there is no place for a business analyst on their team. Joy Beatty and James Hulgan, both experienced agile consultants, refute this belief and explain how business  analysts can enhance the effectiveness of most any agile team.

Joy Beatty's picture Joy Beatty James Hulgan
Painful Lessons I Learned From Bootstrapping a Startup

If you are considering leaving the nest to self-fund your own endeavor, you may want to read about Mike Botsko's experience creating a cloud-based, bug-tracking app called Snowy Evening. What started out as a lot of fun quickly turned into a tough journey. Don't worry—it has a happy ending!

Mike Botsko's picture Mike Botsko
How Can You Get More Effective with DevOps?

By emphasizing better communication and collaboration between software development and IT, this article explores ways to establish trust by focusing on customer value. For example, Manoj Khanna suggests continuous integration and validation as techniques that helps build that trust.

Manoj Khanna's picture Manoj Khanna
Requirements Reuse: Fantasy or Feasible?

Software development teams think nothing about reusing code, but what about requirements? The benefits include faster delivery, lower development costs, consistency across and within applications, fewer defects, and reduced rework.

Karl E. Wiegers's picture Karl E. Wiegers Joy Beatty

Interviews

The "Show Me the Money" Approach to Software Development: An Interview with Michael Harris
Podcast

In this interview, Michael Harris, the president and CEO of David Consulting Group, explains his five-step Value Visualization Framework. He discusses how he came up with the idea, how it can help your team right now, and its similarities to the agile methodology.

Josiah Renaudin's picture Josiah Renaudin
STAREAST 2015 Interview with Rob Sabourin on Exploring Usability Testing for Mobile and Web Technologies
Video

In this interview, Rob Sabourin talks about his STAREAST presentations. These cover how to elicit effective usability requirements with storyboarding and task analysis, and how to blend the requirements, design, and test cycles into a tight feedback loop.

Jennifer Bonine's picture Jennifer Bonine
Acceptance Test-Driven Development and Communication in Agile: An Interview with Jared Richardson
Podcast

In this interview, principal consultant and Agile Artisans founder, Jared Richardson, explains how misunderstanding requirements can cause major issues within an organization. He covers why team members need to communicate, how big projects are often mishandled, and the value of agile.

Josiah Renaudin's picture Josiah Renaudin
How Agile Helped a Business Analyst Discover Her True Value: An Interview with Diane Zajac-Woodie
Video

Diane Zajac-Woodie sat down to discuss her upcoming presentation at Agile Development and Better Software Conference West 2014, why the business analyst role doesn't get the attention it deserves, how the BA role can make a difference on agile teams, and her alter ego as the Agile Squirrel.

Conference Presentations

The Business Analyst’s Critical Role in Agile Projects
Slideshow

Are you a business analyst, wondering how you fit into agile projects? Are you a ScrumMaster who wants to work with business analysts for a stronger project team? Are you a product owner who needs to supercharge your product backlog? Mark Layton introduces you to the critical role of the...

Mark Layton, Platinum Edge, Inc.
STARCANADA 2013: Quantifying the Value of Static Analysis
Slideshow

During the past ten years, static analysis tools have become a vital part of software development for many organizations. However, the question arises, “Can we quantify the benefits of static analysis?” William Oliver presents the results of a Lawrence Livermore National Laboratory study...

William Oliver, Lawrence Livermore National Laboratory
The Right Question for the Right Requirements
Slideshow

How often have you gone down the road of developing software almost to completion only to discover new requirements that require significant design and coding changes at the last minute? Requirements analysis is not just writing down what customers say they want. It's about digging down and discovering what they need. Without real analysis, our requirements often end up as poorly defined lists, anemic mock-ups, and incomplete or inconsistent models. Jack Jones spotlights one simple technique to discover these needs: Ask "why?" When the customer states a requirement, ask "why?" to delve down a level to discover their real problem, need, or opportunity. You may find you need to repeat "why?" a number of times. Join Jack to explore the very real consequences of not comprehending customer needs early in the process, and practice better communications techniques to avoid unnecessary requirements and scope changes.

Jack Jones, KMI
Better Software Conference East 2012: Data Collection and Analysis for Better Requirements
Slideshow

According to the Standish group, 64 percent of features in systems are rarely-or never-used. How does this happen? Today, the work of eliciting the customers' true needs, which remains elusive, can be enhanced using data-driven requirements techniques. Brandon Carlson introduces data collection approaches and analysis techniques you can employ on your projects right away. Find out how to instrument existing applications and develop new requirements based on operational profiles of the current system. Learn to use A/B testing-a technique for trying out and analyzing alternative implementations-on your current system to determine which new features will deliver the most business value. With these tools at hand, you can help users and business stakeholders decide the best approaches and best new features to meet their real needs. Now is the time to take the guesswork out of requirements and get "Just the facts, Ma'am."

Brandon Carlson, Lean TECHniques, Inc.

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.