Showcase in Agile Methodology

Showcase is very important in agile product development. It lets the product development team project the work they have done so far in front of the stake holders or the potential end users or business users. Primarily showcase is done to take early feedback and reduce the last minute surprises. It’s also done to find out if the Product Development team is building the product right.

Why some of the show case results in too much of feedback/comments or sometimes creation of some other story cards or Change Requests? This blog article is to share my views and opinion on the same. Ideally when business analyst (BA) write down the narratives or story, they generally get it reviewed by the client. I suppose the BA do their homework before presenting the narrative to the client. So the question is even though the narratives are approved by the clients, why the showcase fails (a harsh word to use)? There could be many reasons but as per my understanding I feel there are only 2 prominent reasons.

The first reason I see is : when client actually see the developed functionality they realize that this is not what they wanted or it could have been developed better with some more enhanced functionalities. Prototypes actually help you think better and decide. And so the importance of prototyping cannot be ignored. Second reason is: when business analyst (BA) discusses the story with a bunch of developers and testers, sometimes it so happens that developers points out some technical difficulty in implementing the story. So BA (who supposedly should represents Customer) get convinced and compromises. This not only leads to the deviation from the original story but also changes the way we should implement the story. Sometimes we do this to get feedback, but most of the time this results in lot of re-work both from development and testing point of view.

So a noisy* showcase will always end up in creation of Change Requests.   :)

 

* Noisy here means showcase with too much of comments/feedbacks.

Comments

  1. AnonymousJuly 20, 2010

    I feel Agile supports early feedback and accommodating a CR should not be any problem in agile as compared to their traditional counterpart.

    Vijay

    ReplyDelete

Post a Comment

Your comments will be reviewed and then published !

Popular posts from this blog

The 3 qualities that will always help you become better at almost anything…

Image
Have we ever noticed how excited we are when we start anything? But it’s a sad fact that 70% of people abandon what they have started with so much energy and love. It could be as small as building a hobby or starting a pet project or even an activity or a side learning we started. “ Well begun is half done .” Aristotle did say this but we are judged for how we have finished something. You separate yourself fro m  the masses when you choose to give that task a finish.  The first quality is finishing off what you started and it helps develop mental stamina or willpower.   It builds confidence and inculcates as a habit in a long run. You don’t need to sign up for the mammoth activity to build this habit, even finishing mundane day-to-day routine tasks will help. Diligence — the quality of working carefully and with a lot of effort Diligence is a quality that almost never will get unnoticed. It’s one of the underlying traits of grea...
Read More »

Embracing the Journey: Finding Joy in the Process

Image
 In our fast-paced world, it’s easy to get caught up in chasing our goals. Whether it's a career milestone, a fitness target, or a financial aim, we often fixate on the end result. But recently, I came across a quote by Sal Di Stefano that struck a chord with me: “The man who loves walking will walk further than the man who loves the destination.” Rediscovering the Joy of the Journey This quote reminded me of something profound – the importance of loving the journey, not just the destination. When we enjoy the process itself, we find a deeper, more sustainable source of motivation. This mindset can be a game-changer, not just professionally but personally as well. A Personal Anecdote: My Professional Journey Let me share a bit of my own experience. As a software engineer turned entrepreneur, I initially focused heavily on the end goals: launching the company, acquiring clients, and hitting revenue targets. But over time, I realized that what kept me going during tough times was not...
Read More »

How to install Android Emulator on Windows

Image
As part of my testing work, I am currently working on using webdriver to test on Android. So I had to install Android Emulator on Windows 7. Below are the sequential steps and I hope it will ease some pain on getting Android emulator on your Windows 7 box. Download the installer from http://developer.android.com/sdk/index.html Install it to a location (like: C:\Program Files\Android) Launch “SDK Manager.exe” It will launch a “Android SDK and AVD Manager”. By default “Installed packages” will be highlighted. On the pop up “Choose Packages to Install”, there will be some packages selected already. Go ahead with the “Install”. 4.    Once it is done, select “Virtual Devices” to create one for you. Click on “New” and enter some name. Target as “Android 2.2 – API Level 8”. Select Size as “512” and “ Built-in ” to be “WVGA854” and click on “ Create AVD ”. 5. Once done select the Virtual device you created and click on Start . You can find the “Start” button on t...
Read More »