Using Scrum on Larger Projects: 'Scrum of Scrums'

by Kelly Waters (2009-06-10)
Rating 5.0 out of 5 (1 rating) read comments

A technique for scaling Scrum up on larger projects…

To Estimate or Not To Estimate, That is the Question

by Kelly Waters (2009-06-01)
Rating 5.0 out of 5 (1 rating) read comments

Does estimating add value, or is it waste?

Agile Project Management & Product Strategy - A Case Study

by Eric D. Brown (2007-08-08)
Rating (0 ratings) read comments

A short case study on the benefits of approaching product development with an agile mindset. This article describes the redesign of a product development plan from a waterfall approach to a more agile approach.

After redesigning the development plan, the company was able to release a product in half the time (6 months compared to 12 months) and capture ~$3.5 million in revenue.

In addition to the web-based article, a PDF version is available.

Agile Requirements, In Context

by Ellen Gottesdiener (2008-01-30)
Rating (0 ratings) read comments

How do you “do” agile requirements when your product is large and complex? Can you strike a balance between gaining upfront understanding of product requirements while honoring the agile imperatives for delivering business value and iterative development?

Agile requirements need to be understood in context of the product, release, and iteration. In this article, Ellen Gottesdiener shares how to develop requirements on large agile projects – just enough requirements, just in time.

Requirements Practices in Agile Projects

by Ellen Gottesdiener (2007-09-27)
Rating (0 ratings) read comments

In this article Ellen Gottesdiener addresses these questions: Do agile projects abandon requirements? Some think so. How do successful agile teams manage requirements? Ellen shares her observations from working with agile teams.

YAGNI Your Requirements Docs

by Ellen Gottesdiener (2007-10-25)
Rating (0 ratings) read comments

This article addresses the topic of requirements documentation. How useful is yours? Do you produce dense and voluminous requirements documentation that doesn’t provide business value? How much is too much – or too little? What questions can you ask yourself to make good choices about requirements documentation? Ellen Gottesdiener explores how you can leverage the YAGNI principle from eXtreme Programming (XP) for making good choices about your requirements documentation. Read on…

Guerrilla Facilitation

by Ellen Gottesdiener (2008-10-28)
Rating (0 ratings) read comments

Ever feel frustrated that you can’t intervene during meetings gone astray? How can you take action when you’re not the designated facilitator or “one in charge”? In this month’s article, I explore specific ways you conduct “guerrilla facilitation” to help your group collaborate. Read on…

The Agile Business Analyst: Eyes for Waste

by Ellen Gottesdiener (2009-02-04)
Rating (0 ratings) read comments

As an agile analyst, you know how easy it is to get lost in a blizzard of project details. The way to keep focused is to remind yourself of the chief reason for using agile processes: to deliver business value for your organization. With that in mind, we’ll look at specific ways you can combine two approaches: agile and lean. Read on…

What's Going Right Around Here? Using AI to Improve Your Agile Requirements Process

by Ellen Gottesdiener (2009-01-24)
Rating (0 ratings) read comments

Instead of focusing on the problems, focus on what works. That is the simple premise of “appreciative inquiry.” In this week’s column, Ellen Gottesdiener explains how to help your team focus on the processes that work by outlining what should be included in your appreciative inquiries, in order to make more positive organizational changes.

Agile Business Analysis in Flow - The Work of the Agile Analyst (Part 1)

by Ellen Gottesdiener (2009-05-09)
Rating (0 ratings) read comments

Agile is here, and it’s coming soon to an organization near you-if it’s not already there. As a business analyst, are you ready to make the transition to this value-centered development approach? How will your role change? What will you do differently? What will you actually do as part of an agile team? What agile analysis practices might you adapt if you’re working on a traditional (waterfall-style) project?

In short, how can you make yourself more valuable to your agile team and organization using your business analysis skills and abilities? Read on…