Identify the states in your development workflow. You can replicate your existing states, or refine your current practices when configuring the lifecycle in Serena Business Manager. Questions you might hear include:
Who submits new requests for different types of work (such as features, defects, etc.) to your development team, and in what form?
What is involved with design and analysis of new features, before developers actually begin work? Who is responsible?
How is testing managed? Is it part of the development effort, completed afterwards, or both? Who manages the test states?
What steps are required in order to certify new work for release? Consider such things as stabilization, defect burndown sprints, and deploying to staging. Who manages these steps?
Best Practices for Defining Your Workflow
You can customize the workflows in Serena Development Manager as needed. Study and work with the out-of-the-box workflows, itemize the changes that you need to make, and update them using Serena Business Manager Composer.
Integrate testing into your development lifecycle. Out-of-the-box, the Serena Development Manager workflow includes a separate state for testing that occurs after development is complete. However, we strongly advocate for testing in context of development. Developers should test their own work, as well as peer review each other’s work.