742:
stakeholders decide to relocate project into exception, a detailed exception plan is needed to be introduced which will replace the versions of the project/stage plans which were in use before the exception. And on top of all this additional paperwork, the project manager will also have to keep the project moving forward and ensure their team is motivated. Once the project initiation document is formally approved, it means that there is an additional contingency to utilize before having to move into exception. This can make all the difference to the successful delivery of a project in much the same way as good cash flow is key to the success of any growing business.
759:
that your project initiation document will be of a sufficient standard to be approved and passed onto the programme board for funding. Depending on the complexity and the size of the project the stages are about to be completed in five informal and four formal reviews. Some problems could appear such as shortage or resources and lack of finance. It is pivotally important to identify how prioritized is your project before starting the project initiation document, which will help to avoid huge expenses if the project is about to appear in an exception stage.
521:
project initiation document also includes the date when the project initiation documentation was approved by the project board. The project initiation document is not regularly updated during project stages. Any revisions or updates which are needed are to be done at the end of the each stage in order to incorporate detailed milestones for the next steps. The project initiation document is the basis of decisions taken for the project and it is unhelpful when the document is queried or altered at a later stage with no reference to why, by whom or when.
729:, project stages and exception process. Those could include budget actuals and forecasts produced for each financial period, exceptions to be escalated to the corporate programme manager, product reviews from the quality plan, project tolerance, risk mitigation plan, identifying project risks and plans for their mitigation, an issues log, existing change control processes, weekly highlight report for corporate program board, weekly supplier meetings, weekly project teams meetings, etc.
617:. A project may be achieved by a cross-functional team with experienced representatives from multiple departments including development, interactive, test, networking, infrastructure and business systems, security and marketing. The involvement of the different areas will vary as the project progresses of the initial project. The SMG (Senior Management Group) will be notified of key findings and developments.
768:
documentation represents the understanding of the background, objectives and benefits. A good project manager is not only interested in delivering an output or a capability to their customer, but interested in the wider context and the benefits that this capability will ultimately bring about. The project initiation documentation identifies what is in scope within the project with the use of
234:
132:
36:
575:
played a pivotal role in project participation should be mentioned in this section of the project initiation document. It is a rational way of make the specific project above others emphasizing the attention of participation of most active candidate of a team. It is because someone important within the company wants to see it. The result should be that the
77:
481:. In short, this is the, "who, why, and what", part of the project. It defines all major aspects of a project and forms the basis for its management and the assessment of overall success. The project initiation document builds upon the business case (if it exists) using the information and analysis data produced during initiation activities.
717:
the scope. Relaunching date or reducing the scope need to be supported with justifications, on which stakeholders making a decision of delaying the launch date. The sooner the worker starts building that sort of relationships with stakeholders, the easier it will be later on when more pressing concerns regarding the scope are raised.
716:
implies adequate reconsideration of proposed date and detail phases accordingly. Often business stakeholders ask projects to be delivered to impossible dates, which requires highlighting of that fact. In that case most of stakeholders are flexible and about to reconsider the launch date or reducing
758:
by e-mails with the request of comments. Then the lead of the team will amass the comments, and then it will be followed by the final meeting where stakeholders and interested parties are about to discuss the project initiation document in further detail. It is only after these stages are complete
574:
establishes why and how the project was created. Phase 1 of the project will deliver the online functionality required together with the changes to the necessary business systems impacted, whilst phase 2 will deliver the digital rights management and real-time advert insertion. The person, who has
549:
explains what innovations, changes and aspects the project will bring within the environment and the society and which changes and renewals it will cause. The project scope statement should include as much detail as possible, as it helps to avoid proliferating problems and questions in the project
520:
and state what the project is aiming and planning to achieve and the reason for the importance of meeting these aims. It also contains the list of people who are participating in the project development from the very beginning until project closure, along with their roles and responsibilities. The
741:
are initiation, requirements, design, development, test, project launch and close with the exception process stage. The last stage is the most unstable, as covers how much the budget, time and project scope could increase without the project being forced to go into exception. In a situation when
767:
Specifying the importance of the project, the project initiation documentation identifies that it is the contract between the project management and sponsor. The aim of the project initiation documentation is understanding the premises of the project. The correct format of project initiation
476:
The project initiation documentation bundles together documentation to form the logical document that brings together all of the key information needed to start and run the project on a sound basis. It should be conveyed to all stakeholders and agreed and signed off by the
692:(ESA) will be taking place. These are basically checkpoints during the life of the project which ensure that a quality product is being delivered. ESA's implies the meeting where considering the baselined project plan to ensure that it is up to date and on
753:
The last stage of writing a project initiation document is the approval, which implies the distribution to all stakeholders on the distribution list within the project initiation document and other interested parties such as operations or
469:, and any specific project controls or inspections as part of a departmental quality plan or common project approach. The project initiation documentation represents a detailed version of the basic project start-up document called the
440:
could be created instead of a project initiation documentation; the two document types are highly similar. But a project charter is less detailed, which makes it more suitable for cases in which content producers are less available.
375:
controlled project environment. PRINCE2's 2009 renaming "document" to "documentation" indicates a collection of documentation that has been collected up creating a project rather than all the information in the system.
812:
Risks are needed to be identified before they appear as a problem within the whole project. The problem could be resolved by creating the list of top projects' risks and what precautionary measures have to be taken.
816:
The financial side of the project is needed to be considered. The project initiation documentation scheme needs to be included along any budgetary constrains and provided the assumptions the team used when they
629:, lead architects and team leaders where discussions of project management reports, weekly project team meetings, fortnightly supplier meetings and weekly programme board meetings will take place.
516:
The purpose of the project initiation document is to capture and record basic information needed to correctly define and plan the project. The project initiation document should expand upon the
745:
Boehm has identified six risk management stages: Identification, assessment, prioritisation, management planning, resolution and monitoring, which take place in project initiation document.
809:
The success of the project initiation document and the whole project can build up on visual aspects such as graphics, as a way of galvanizing better visual memorizing of the project.
95:
251:
49:
821:
as well as details about how often the review will be estimates. The important aspect should avoid isolations, as it might cause mistakes such as spelling or jargon.
911:
298:
196:
971:
887:
270:
168:
55:
625:
During the whole process of creating the project initiation document the project manager is aware that they will be attending meetings with
605:
in the project initiation document identifies the outer impact, such as unavailability of resources or a competitor (e.g. another project).
795:
and creating a project initiation document, such as: how will the project be delivered? What type of approach: variegates techniques (e.g.
1034:
1007:
545:. This is the part of the project initiation document explaining in depth what the project is delivering for stakeholders and customers.
664:
277:
175:
824:
In order to improve the project initiation documentation, a presentation could be created, identifying and emphasizing on main points.
806:
For a project initiation document it is sufficient to include the place, which emphasize on main phases and activities of the project.
995:
983:
935:
947:
923:
335:
317:
215:
113:
63:
153:
146:
284:
182:
899:
818:
588:
503:
The project initiation document provides a reference point throughout the project for both the customer and the project team.
453:
term representing the plan of approach in project management. It is assembled from a series of other documents, including the
489:
266:
255:
164:
1049:
640:
is usually written by the IT quality assurance (ITQA) and identifies aspects which will be delivered as part of a project (
693:
576:
773:
912:
http://www.my-project-management-expert.com/writing-a-project-scope-statement-in-a-project-initiation-document.html
800:
393:
357:
867:
244:
142:
379:
The project initiation document provides a reference point throughout the project for both the customer and the
725:
There are specific number of sections, which needed to be completed in terms of controlling the whole project:
696:, project management reports, project workstream checkpoint reports, team meeting minutes, actions and agenda,
529:
Project scope statement is one of the most important sections of the project initiation document. The project
291:
189:
697:
972:
http://www.my-project-management-expert.com/writing-a-project-initiation-document-communications-plan.html
626:
776:. The pivotal role plays the identification of responsibilities, which implies roles of project manager,
646:
406:
1035:
http://www.my-project-management-expert.com/project-lifecycle-project-initiation-document-approval.html
1008:
http://www.my-project-management-expert.com/writing-a-project-initiation-document-project-controls.html
726:
614:
411:
996:
http://www.my-project-management-expert.com/writing-a-project-initiation-document-initial-plan.html
984:
http://www.my-project-management-expert.com/writing-a-project-initiation-document-quality-plan.html
470:
936:
http://www.my-project-management-expert.com/writing-a-project-initiation-document-assumptions.html
948:
http://www.my-project-management-expert.com/writing-a-project-initiation-document-governance.html
924:
http://www.my-project-management-expert.com/writing-a-project-initiation-document-background.html
843:
785:
593:
458:
421:
361:
17:
591:
and constraints detail the project initiation document. Those details are assumed ahead of the
883:
803:)? What ways of communication with stakeholders, keeping on top of risks, issues and changes.
658:
478:
367:
The project initiation documentation bundles the information, which was acquired through the
1067:
900:
http://www.my-project-management-expert.com/writing-a-project-initiation-document-intro.html
848:
796:
755:
559:
530:
517:
437:
1050:
http://www.susannemadsen.co.uk/blog/what-makes-a-perfect-project-initiation-document-pid
416:
1061:
833:
737:
The rule says the more we are about to commit, the more we will need to deliver. The
462:
454:
401:
769:
466:
380:
777:
233:
131:
781:
701:
613:
In order to complete the organization stage, the team needs to complete the
959:
652:
579:
and equipment are made available to you to ensure your project happens.
838:
792:
738:
485:
450:
372:
368:
791:
There are key aspects which need consideration before starting a
562:
to make decisions of financial aspects and projects' expenses.
227:
125:
70:
29:
386:
A project initiation document often contains the following:
550:
lifecycle (requirements are needed in order to succeed in
364:, which provides the foundation for the business project.
1048:
What makes a perfect
Project Initiation Document (PID)?,
91:
868:
Project
Initiation and the Project Initiation Document
496:(IP) process. It is the document that goes before the
484:
A common part of formal project methodologies such as
445:
Project initiation documentation in terms of PRINCE2
784:, user representative, stakeholders and members of
258:. Unsourced material may be challenged and removed.
86:
may be too technical for most readers to understand
934:Assumptions, Dependencies and Constraints of PID,
371:(SU) and initiating a project (IP) processes in a
882:Prince 2: A Practical Handbook By Colin Bentley,
714:initial plan for project initiation documentation
1033:Getting a Project Initiation Document Approved,
1023:. Washington D.C.: IEEE Computer Society Press.
763:Characteristics of project initiation document
749:Getting a project initiation document approved
8:
64:Learn how and when to remove these messages
449:The project initiation documentation is a
583:Assumptions, dependencies and constraints
336:Learn how and when to remove this message
318:Learn how and when to remove this message
216:Learn how and when to remove this message
114:Learn how and when to remove this message
98:, without removing the technical details.
960:https://www.rbkc.gov.uk/pdf/jsna_pid.pdf
898:Purpose of PID and Related documents, .
860:
152:Please improve this article by adding
1044:
1042:
946:Project Organization and Governance,
922:Project Backgrounds in Terms of PID,
688:). The ITQA also determines when the
507:Writing a project initiation document
96:make it understandable to non-experts
27:Crucial process of a business project
7:
958:Draft Project initiation Document,
500:for sign off to commence a project.
256:adding citations to reliable sources
599:business requirements specification
267:"Project initiation documentation"
165:"Project initiation documentation"
25:
356:) is one of the most significant
45:This article has multiple issues.
910:Project Scope Statement in PID,
232:
130:
75:
34:
18:Project Initiation Documentation
594:project management requirements
243:needs additional citations for
53:or discuss these issues on the
465:, the project tolerances, the
461:, the communication plan, the
1:
533:is divided into three parts:
154:secondary or tertiary sources
774:product breakdown structures
733:Initial risks and issues log
627:third party project managers
543:in scope for project example
609:Organization and governance
1084:
1006:Project Controls in PID,
704:, and a quality plan tip.
665:software requirements spec
872:Retrieved on June 3, 2010
1021:Software Risk Management
488:the document is a major
678:post development review
535:Project scope statement
525:Project scope statement
994:Project Initial Plan,
982:Project Quality Plan,
642:baselined project plan
350:project documentation
141:relies excessively on
647:business requirements
369:starting up a project
1019:Boehm, B.W. (1989).
970:Communication Plan,
708:Initial project plan
690:end stage assessment
686:project quality plan
638:Project quality plan
494:initiating a project
426:Reporting frameworks
398:Project organization
252:improve this article
603:Project constraints
844:Project management
786:steering committee
621:Communication plan
615:organization chart
601:being documented.
572:project background
566:Project background
459:terms of reference
362:project management
888:978-0-7506-5330-5
801:agile methodology
682:stage assessments
659:high level design
552:in scope category
547:Proposed solution
539:proposed solution
479:business sponsors
346:
345:
338:
328:
327:
320:
302:
226:
225:
218:
200:
124:
123:
116:
68:
16:(Redirected from
1075:
1052:
1046:
1037:
1031:
1025:
1024:
1016:
1010:
1004:
998:
992:
986:
980:
974:
968:
962:
956:
950:
944:
938:
932:
926:
920:
914:
908:
902:
896:
890:
880:
874:
865:
849:Project planning
756:HR for resources
727:project controls
721:Project controls
558:phase helps the
422:Project controls
341:
334:
323:
316:
312:
309:
303:
301:
260:
236:
228:
221:
214:
210:
207:
201:
199:
158:
134:
126:
119:
112:
108:
105:
99:
79:
78:
71:
60:
38:
37:
30:
21:
1083:
1082:
1078:
1077:
1076:
1074:
1073:
1072:
1058:
1057:
1056:
1055:
1047:
1040:
1032:
1028:
1018:
1017:
1013:
1005:
1001:
993:
989:
981:
977:
969:
965:
957:
953:
945:
941:
933:
929:
921:
917:
909:
905:
897:
893:
881:
877:
866:
862:
857:
830:
765:
751:
735:
723:
710:
635:
623:
611:
585:
568:
560:project manager
531:scope statement
527:
518:project mandate
514:
509:
447:
438:project charter
342:
331:
330:
329:
324:
313:
307:
304:
261:
259:
249:
237:
222:
211:
205:
202:
159:
157:
151:
147:primary sources
135:
120:
109:
103:
100:
92:help improve it
89:
80:
76:
39:
35:
28:
23:
22:
15:
12:
11:
5:
1081:
1079:
1071:
1070:
1060:
1059:
1054:
1053:
1038:
1026:
1011:
999:
987:
975:
963:
951:
939:
927:
915:
903:
891:
875:
859:
858:
856:
853:
852:
851:
846:
841:
836:
829:
826:
764:
761:
750:
747:
739:project stages
734:
731:
722:
719:
709:
706:
634:
631:
622:
619:
610:
607:
584:
581:
567:
564:
526:
523:
513:
510:
508:
505:
446:
443:
434:
433:
430:
427:
424:
419:
414:
409:
404:
399:
396:
391:
344:
343:
326:
325:
240:
238:
231:
224:
223:
138:
136:
129:
122:
121:
83:
81:
74:
69:
43:
42:
40:
33:
26:
24:
14:
13:
10:
9:
6:
4:
3:
2:
1080:
1069:
1066:
1065:
1063:
1051:
1045:
1043:
1039:
1036:
1030:
1027:
1022:
1015:
1012:
1009:
1003:
1000:
997:
991:
988:
985:
979:
976:
973:
967:
964:
961:
955:
952:
949:
943:
940:
937:
931:
928:
925:
919:
916:
913:
907:
904:
901:
895:
892:
889:
885:
879:
876:
873:
869:
864:
861:
854:
850:
847:
845:
842:
840:
837:
835:
834:Business case
832:
831:
827:
825:
822:
820:
814:
810:
807:
804:
802:
798:
794:
789:
787:
783:
779:
775:
771:
770:flow diagrams
762:
760:
757:
748:
746:
743:
740:
732:
730:
728:
720:
718:
715:
707:
705:
703:
699:
695:
691:
687:
683:
679:
675:
671:
667:
666:
661:
660:
655:
654:
649:
648:
643:
639:
632:
630:
628:
620:
618:
616:
608:
606:
604:
600:
596:
595:
590:
587:Assumptions,
582:
580:
578:
573:
565:
563:
561:
557:
553:
548:
544:
540:
536:
532:
524:
522:
519:
511:
506:
504:
501:
499:
498:project board
495:
491:
487:
482:
480:
474:
472:
471:project brief
468:
464:
463:risk register
460:
456:
455:business case
452:
444:
442:
439:
431:
428:
425:
423:
420:
418:
415:
413:
410:
408:
405:
403:
402:Business case
400:
397:
395:
392:
390:Project goals
389:
388:
387:
384:
382:
377:
374:
370:
365:
363:
359:
355:
351:
340:
337:
322:
319:
311:
300:
297:
293:
290:
286:
283:
279:
276:
272:
269: –
268:
264:
263:Find sources:
257:
253:
247:
246:
241:This article
239:
235:
230:
229:
220:
217:
209:
198:
195:
191:
188:
184:
181:
177:
174:
170:
167: –
166:
162:
161:Find sources:
155:
149:
148:
144:
139:This article
137:
133:
128:
127:
118:
115:
107:
97:
93:
87:
84:This article
82:
73:
72:
67:
65:
58:
57:
52:
51:
46:
41:
32:
31:
19:
1029:
1020:
1014:
1002:
990:
978:
966:
954:
942:
930:
918:
906:
894:
878:
871:
863:
823:
815:
811:
808:
805:
790:
766:
752:
744:
736:
724:
713:
712:Writing the
711:
698:project risk
689:
685:
681:
677:
673:
670:test scripts
669:
663:
657:
651:
645:
641:
637:
636:
633:Quality plan
624:
612:
602:
598:
592:
589:dependencies
586:
571:
569:
555:
551:
546:
542:
538:
534:
528:
515:
502:
497:
493:
483:
475:
467:project plan
448:
435:
429:PID sign off
412:Stakeholders
385:
381:project team
378:
366:
353:
349:
347:
332:
314:
305:
295:
288:
281:
274:
262:
250:Please help
245:verification
242:
212:
203:
193:
186:
179:
172:
160:
140:
110:
101:
85:
61:
54:
48:
47:Please help
44:
780:, sponsor,
778:team leader
674:test report
407:Constraints
855:References
702:issues log
308:April 2017
278:newspapers
206:April 2017
176:newspapers
143:references
104:April 2017
50:improve it
797:waterfall
653:use cases
577:resources
490:milestone
358:artifacts
56:talk page
1062:Category
828:See also
819:estimate
782:supplier
694:schedule
556:in scope
1068:PRINCE2
839:PRINCE2
793:project
680:(PDR),
668:(SRS),
662:(HLD),
650:(BRS),
554:). The
512:Purpose
492:in the
486:PRINCE2
451:PRINCE2
432:Summary
373:PRINCE2
292:scholar
190:scholar
90:Please
886:
457:, the
294:
287:
280:
273:
265:
192:
185:
178:
171:
163:
684:in a
417:Risks
394:Scope
299:JSTOR
285:books
197:JSTOR
183:books
884:ISBN
772:and
700:and
597:and
570:The
541:and
348:The
271:news
169:news
360:in
354:PID
254:by
145:to
94:to
1064::
1041:^
870:-
799:,
788:.
676:,
672:,
656:,
644:,
537:,
473:.
436:A
383:.
156:.
59:.
352:(
339:)
333:(
321:)
315:(
310:)
306:(
296:·
289:·
282:·
275:·
248:.
219:)
213:(
208:)
204:(
194:·
187:·
180:·
173:·
150:.
117:)
111:(
106:)
102:(
88:.
66:)
62:(
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
