Steve sounds to me like simply a mix of Mitch and Peter, rather than a seperate persona.
Steve needs to _Manage_ his modules, while also needing to Code for them. And has a bit of an average QA in him in terms of being interested in other Modules which use/are used by his. --Justin Wood (Callek) 19:30, 26 June 2006 (PDT)
- In real life, those it is a different person. In all companies I worked at, we had at least one senior engineer. He was responsible for the team of coders, or not, but he always had his modules to care about (own them, manage them, set vision and directions), and was also coding.
- There's a huge difference (also in the way of how you use Bugzilla) if you're project/product manager, and module manager. Product/project manager doesn't care about the module consistency, API, vision of development, ABI, etc. He cares if there are no crashers, bugs are solved fast, features are implemented etc. Module owner cares about any single change that happens to his module. --gandalf 19:05, 27 June 2006 (PDT)
Personas are not people or job titles, they are roles. If it's true that Steve simply does some of the tasks Mitch does, and some of the tasks Peter does, then there's no need to have him as a separate persona, even if he is a separate person.
If the issue here is that you think one of the personas needs to have a requirement to understand the bug state of a "module" (do you mean Component?) that he owns, then we can add that to one of them without needing a whole new persona.
Gerv 08:53, 14 July 2006 (PDT)