I'd say the complete Out of Scope section should include a list of the out of scope process steps and inputs. That seems to capture the core elements that need to be documented in that section.
The key is to make sure the Out of Scope section covers all the bases - the specific process steps that are out of scope, the rationale for why they're out of scope, and how that affects the overall to-be process. That's the best way to demonstrate a thorough understanding.
Hmm, I'm a bit unsure on this one. I think it might just be a simple list of the out of scope process steps, but I'm not 100% sure. I'll have to review the PDD guidelines again to be certain.
I'm pretty confident that the complete Out of Scope section should list out of scope process steps, the reason for them being out of scope, and the impact on the to-be process. That seems like the most comprehensive approach.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Fletcher
2 months agoJoaquin
2 months agoJonelle
3 months agoLouvenia
3 months agoCarri
3 months agoGlen
3 months agoJacki
4 months agoRosalyn
4 months agoCandida
4 months agoJovita
4 months agoTenesha
4 months agoDominga
4 months agoYuki
5 months ago