Archive for the ‘Stakeholders’ Category

Focus on Value: 4 Factors Every Team Should Consider

Tuesday, June 17th, 2014

1Most of our clients share the same goal: deliver value. Yet often we find that these same clients cannot define what value looks like for their companies, or determine how to use value to inform project decisions.

We’ve identified 4 key factors to help your team bring value into focus:

  • Involve the Right People
  • Define Value Transparently
  • Look Toward the Short Term
  • Have the Vision to Change

Involve the Right People

Defining a product’s desired result, before building it, is fundamental to that product’s success. To do this successfully, you need to identify all of the key stakeholders from the customer, business, and technology realms. These stakeholders need to work together, as collaborating product partners, to envision the product, define goals, and specify measurable objectives, thereby creating a high-level view of the desired product outcomes. Having these key markers will ensure that the team is always building the most valuable thing. Continue reading

Rope Your Scope: Reining in Scope Creep (Part II)

Wednesday, June 19th, 2013

Slide1Last time, I told the story of a team that experienced a breakthrough after clarifying the scope of a stalled project. Noting that scope creep—the unrestrained expansion of requirements as the project proceeds—is cited as one of the top project risks, I promised to describe some of the good practices that help product partners manage product scope in a disciplined way. With clients, I always stress the importance of developing a product vision, identifying goals and objectives for the product, and clarifying the product partners’ value considerations very early in the project before development proceeds. Let’s look at ways to do that. Continue reading | 1 Comment

Rope Your Scope: Reining in Scope Creep (Part I)

Thursday, May 9th, 2013

scope creep image 2- contextRecently I worked with a project team developing a software product under grant from four entities, with a government agency as their ultimate customer. They called me in because, three months into a four-month project, they were desperately behind. Why? They’d been spinning in circles, trying to satisfy diverse stakeholders who had overlapping as well as conflicting requirements. The funding was split among several competitors, each with its own competencies, and there was a sense that the government agency was playing favorites based on its own preferences in the domain. Continue reading

Cure Your Agile Planning and Analysis Blues: The Top 9 Pain Points

Tuesday, March 5th, 2013

frazzledproductchampionIf you’re on a team that’s transitioning to lean/agile, have you experienced troubling truths, baffling barriers, and veritable vexations around planning and analysis? We work with many lean/agile teams, and we’ve noted certain recurring planning and analysis pain points.

Mary Gorman and I shared our top observations in a recent webinar. Our hostess, Maureen McVey, IIBA’s Head of Learning and Development, prompted us to begin by sharing why we wrote the book Discover to Deliver: Agile Product Planning and Analysis and then explaining the essential practices you can learn by reading the book. Continue reading | 2 Comments

Agile Product Partners: Friends or Frenemies?

Sunday, November 18th, 2012

It continues to baffle me.

Clients share their struggles managing three, four, or five different product owners (or, as we refer to them, product champions). Delivery teams end up abandoning deployable software right before the end of an iteration or release.

Why?

It’s because the product champions can’t agree among themselves, or with the delivery team, on what to ship. As a result, the team members spend too much time in ineffective meetings and not enough time building high-quality software that delivers value. Continue reading

Experiencing Agile: 6 Agile Planning and Analysis Practices to Try

Monday, May 14th, 2012

What practices can you adopt to help your team experience Agile?

This question was raised by a listener to the podcast we recorded on agile analysis practices with BA coach Yamo. (Find the podcast here.) The specific question that Katie Metcalf asked us was this:

“What Agile techniques would you suggest introducing to a software development team that is currently not using the Agile approach but would like to get a flavor for the methodology?”

Power Up Your Agile Planning & Analysis

Friday, November 18th, 2011

I’m pleased to share my podcast with Jochen (Joe) Krebs*, Founder of Agile NYC. The podcast was recorded on October 11, 2011, just before my presentation to the Agile NYC group.

The presentation, entitled, Power Up Your Agile Planning and Analysis:

Deliver Value via Structured Conversations describes how product stakeholders partner to develop a shared understanding of the product needs. I discuss how the partners gain a focused yet holistic understanding of the highest-value requirements and plan the project so that the delivery team builds the right product, at the right time. Continue reading

This Week’s Business Analysis and Requirements Workshop: 2 Days of Learning in Las Vegas

Tuesday, June 7th, 2011

I was recently interviewed by SearchSoftwareQuality editor Yvette Francino about this week’s Business Analysis and Requirements Workshop at the Better Conference/Development Conference this week in Las Vegas, Nevada (6-7 June, 2011).

Yvette asked me to explain the logistics, if we would be emulating gathering requirements for a particular project and if the workshop be relevant regardless of domain area. Here are my answers: As conference chair, Continue reading | 1 Comment

Are Your Software Development Practices Jumping the Shark?

Thursday, April 7th, 2011

By Ellen Gottesdiener and Mary Gorman

In September 1977, the TV sitcom Happy Days had über-hip Fonzie, clad in leather jacket and swimshorts, water ski over a shark to prove his mettle—and at that moment even diehard fans knew that the show was past its prime. They were right. After that episode, ratings plummeted, and the expression “Jumping the Shark” was born. When a TV show, or anything else, jumps the shark, you know it’s on its way out.

Our question this month: have any of your software development practices jumped the shark?

For example, are there boundaries around people’s roles? Some organizations tend to confine people to roles such as developer, architect… Continue reading