+1 It is similar with the methodic used by OCE (siemens) for for software life cycle. Even more, in EMPOWER we (actually only me) are using the same methodic.
My only comments here are about roles (in software life cycle): Developer - provide the code and evt. the test. It can solve issues. Tester - testing, it It can solve issues. It can re-open issues. Releaser (a.k.a. release manager) - decides what components/test will be included in a release and the degree of maturity for tests. It can solve and it can close issues. Sometime (most of the time) all the roles are played for a single person :). This is similar with what Rupert said. Best Regards, M
