business analysis

Articles

Why Adopting Agile Won’t Magically Reduce Your IT Budget

Of course, all companies would like to reduce their budgets. But cutting back in the IT department can have unintended consequences. This article looks at two of the more well-adopted cost-cutting approaches, the software factory and distributed teams, and goes into how they can help and hurt your company.

Mario Lucero's picture Mario Lucero
Instead of MVPs, Maybe We Should Be Releasing SMURFS

The term minimum viable product, or MVP, has come to be misunderstood and misused in many organizations. It doesn’t mean you should be releasing half-baked, barely feasible software. Instead, you should be thinking of your product’s capabilities as a Specifically Marketable, Useful, Releasable Feature Set—or SMURFS!

Matthew Barcomb's picture Matthew Barcomb
Taking Vision to Reality: Using Agile to Drive Product Delivery

Product development organizations that skip or rush through critical preplanning activities run the risk of failure. Organizations that use a more agile approach to product development ensure that the teams work on the right things, have the right amount of dialogue with their business partners, and produce the right amount of value to the product.

Jack Walser's picture Jack Walser
Making Sense of #NoEstimates

A couple of years ago, the Twitter hashtag #NoEstimates appeared. Its purpose was to start a discussion about alternatives to estimations, but the idea of a project without explicit estimates is odd to most people in software development. However, if you start exploring it, you may find better sources of information to rely on.

Gil Zilberfeld's picture Gil Zilberfeld

Better Software Magazine Articles

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
Moving Beyond the Backlog: The Four Quadrants of Product Ownership

What do you consider the role of product owner in an agile development project to be? Bob presents a compelling perspective that a product owner has four distinct critical roles that can prove impactful to a team's success.

Bob Galen's picture Bob Galen

Interviews

Take a Test Drive: Acceptance Test-Driven Development: 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.

For Maximum Awesome: An Interview with Joe Justice
Video

Joe Justice is a consultant at Scrum Inc. and inventor of the Extreme Manufacturing project management method. He also is the founder of Team WIKISPEED, an all-Scrum volunteer-based, "green” automotive prototyping company.

Cameron Philipp-Edmonds's picture Cameron Philipp-Edmonds
Why the BA Is Essential to Agile Development: An Interview with Steve Adolph
Video

Steve Adolph explains why the BA's role on an agile project cannot be overvalued, due to their immense communication and collaboration skills. Steve describes the best BAs as "boundary spanners" who know the importance of keeping everyone sitting together, and most importantly—talking.

Noel Wurst's picture Noel Wurst

Conference Presentations

The Role of the Agile Business Analyst
Slideshow

The business analyst (BA) role seems conspicuously absent from most agile methods. Does agile make the BA role obsolete? Certainly not! But how does a BA exploit the short cycle times and collaborative nature of agile methods? Drawing from the principles of lean product development flow...

Steve Adolph, WSA Consulting
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.
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

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!