Thanks for the warm welcome.
I see a big problem with the approach you are using for now. It may be
working for now, but with this approach you will always be in reactive
mode. You are reacting to all the bugs that are found and fixing them
based on some priorities. However, bugs are Technical Debt, and you
are not gaining any customer confidence with fixing them either. Our
goal should be to prevent the bugs from occuring in the first place.
The other problem is that you put the system in production/into market
withouth having proper customer inputs. Along with your reactive mode,
you also need to get proactive. Continue using your current approach,
however, along with that, start thinking strategic and be proactive.
Form a panel of customers, call it your 'Product Owner'. Ask the
panel, what they would like to see in the future release and work
towards including those features in the next increment of the product.
I would say define your release to be 90-day. You can have three 3-
week sprints where you complete the development, and use the last 3-
week sprint to complete activities related to releasing the product to
market as well as planning for the next release. With this release
cycle, you could be putting product with improvements and new features
into the hands of your customers every 3 months. They would love to
see the features they sought for, and would be very willing
participant in your release planning.
Hope this helps.
Nimesh Soni
skype: nimesh0308 | twitter: @beyondCSM
Author: "Agile Release Planning" Book:
http://amzn.com/B004TGTHNM
On Jul 29, 2:59 pm, nhm tanveer hossain khan <
hasan8...@gmail.com>
wrote: