Zephyr as applied to Hybrid models
Last Updated on Monday, 12 September 2011 20:13 Written by Ivo Verlaek Monday, 12 September 2011 20:06
| Next > |
|---|
See also: Agile, Waterfall, V-Model, Hybrid Model
Zephyr with its flexible design, easily fits and enhances any test methodology that you might be using as part of your software development lifecycle: Waterfall, Agile, V-Model or a Hybrid.
Zephyr is organized into multiple, logical areas - Department, Projects, Releases/Iterations and has applications in each area that allow for the rigidity of a process flow while keeping the overall model flexible to accommodate changes. This approach leads to effective management of every aspect of your testing department, while giving enhanced productivity and efficiency gains to all members of the department in their day-to-day activities.
Typically, companies are arriving at hybrids of Waterfall, V-Model or Agile software development processes that suit their environment, processes and people best:
- These could be distinct where one team or product line follows a particular process and a second team follows another
- Teams are transitioning from one model to another
- Partners and customers demand a competing model or a variation of an existing model
For its part, the Testing team has to be flexible enough to handle all of these scenarios without having to make major changes to their repositories, tools and reporting mechanisms.
How Zephyr integrates with this process
Zephyr, as a single Test Management System, allows these different models to co-exist peacefully by allowing contextual separation of projects whose internal releases or iterations might follow different software lifecycles while continuing to provide the right visibility into each at the Department level..
