How often do you check a company’s news release section to check the current activity (& energy level of the organization). It is much the same with software. Frequent updates provide a multilevel assurance to customers. It reinforces the view that they are buying into something which is growing, healthy and will evolve with future. It also creates an impression that at least some of changes must be driven by existing or potential clients. This helps reinforce a view that a customer eco-system already exists for the product/service.
Optimal update frequency
The frequency of updates however will depend very much on the life-stage of the product and industry itself. For essentially a bug-fix-release cycle multiple updates in a week should be acceptable. Whereas for a software upgrade release cycle, a once a month or once every two months could more practical. This creates enough deadlines (&milestones) to achieve optimal productivity and to ensure that the product is not much out of sync with the requirements.
Projects/ Product Relevancy
Internal IT applications, utilities, ecommerce projects, small protocol software development projects
Critical Success Factors
The requirement gathering and prioritization is the most important aspect. A practical market / user driven approach is the most beneficial to ensure product success. Ensuring completion of test-cycles is equally important.
Further Questions
Should a software release be primarily bug fix or new feature only?
Should you combine releases, which address different customer-segments?
No comments:
Post a Comment