Product life Cycle

Product automate business domain, normally customizable and charged for additional customization to fit into the particular business needs, where as in project, analysis is based on specific organization needs and then automate accordingly, project may or may not fit to other organization deal with same domain, but product normally do.

Sometimes it is understood that product normally automate business domain or portion of the domain, they may have higher scope than that of projects, and this statement may be true most of the times buts it’s not the rule of thumb, project can have more in scope, size as well, depending upon the nature of the project. again there is misunderstanding product normally automate business domain or portion of the domain, they may have higher scope than that of projects, and this statement may be true most of the times buts it’s can the rule of thumb, project can have more in scope, size as well, depending upon the nature of the project.

Project & products do not have difference as is their development activity is concern, development process of project as well as product is same within the organization, while building a product, focus is more on the scalability & flexibility of the design, software products normally iterates multiple times Software Development Life Cycle while projects normally move to maintenance phase once its delivered, so they are more focused on design keeping the vision of future business plan of the product

Products are triggered normally have some idea or business plan & this business plan originate from organization future business strategies, Idea generation on whiteboards for a new software product, or for the next version of an existing product. On business plan software companies built up the product as per the company software development methodology, different model has been developed for development of the software to cater industry software needs, once the software development gets into build / release cycle, conducts acceptance tests (alpha, beta testing) Once the product is deployed at a customer site, solicit customer feedback, reports defects, and pass these on back to engineering for subsequent build / release cycles, as the product stabilizes, solicit more features and benefits from the users of the software product, users of competitive products, and from analysts and craft / synthesize these requirements for subsequent product build / release cycles, and pass them on to the software engineering team, customer feedback helps to for next version of an existing product or launch brand new product to keep the market need.