|
One thing to remember with adding
additional performers is that we need to identify in the task steps where the role
is included and how that role interacts with other roles. - Jim ____________________ Jim Ruehlin, IBM
Rational RUP Content
Developer Eclipse Process
Framework (EPF) Committer email:
[EMAIL PROTECTED] phone:
760.505.3232 fax:
949.369.0720 From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of "Brian Lyons"
<[EMAIL PROTECTED]> hiho, I like the idea of adding the additional
performers. The original strategy (whether right or
wrong) had been to include an additional performer only if one of the steps can
clearly call out how that person participates. I like the idea of getting
the additional performers on board, but we should adhere to some the strategy
of calling out where that performer fits in. I mention the Analyst in Task: Design
Solution; I’ll add that role in as an additional performer <…
done>. I also had had a notion that the Developer should consider
collaborating with the Tester when Implementing Developer Tests. Tomorrow
I’ll add in some mention of optionally engaging the Tester in the steps
and I’ll add the additional performer. In regard to Scott’s specific
question on bugs, I would personally rather re-open the bugs with a comment of
“add additional performers”, but we could open up new bugs as well.
---------
b From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Per Kroll
epf-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/epf-dev --=_alternative 001AE672882571F8_=-- |
_______________________________________________ epf-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/epf-dev
