You know, I was thinking the same thing. But then I remembered that the 'initiating a project' process is more about the big picture, not the nitty-gritty details. So I'm going to have to go with C - the plan for the work or project initiation.
Hmm, I don't know. B - the need for a configuration library - seems like it could be a valid answer too. Gotta make sure you have the right tools and processes in place before you can really get going, right?
I can see the logic in both of those answers, but I'm leaning more towards A - the agreed project acceptance criteria. Isn't that what you need to establish upfront to make sure everyone's on the same page about what success looks like?
I'm not so sure about that. I was thinking it might be D - an understanding of the project's funding. Knowing where the money is coming from and how much you have to work with seems pretty crucial to getting a project started.
Hmm, this is a tricky one. I feel like the correct answer would be C - a plan for the work or project initiation. That seems to be the core of the 'initiating a project' process.
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
Dorethea
2 days agoArletta
3 days agoCraig
4 days agoJamie
6 days agoNenita
7 days ago