1
00:00:04,990 --> 00:00:12,590
In Project initiation we have two processes create the project charter and identify stakeholders stakeholder

2
00:00:12,590 --> 00:00:13,430
identification.

3
00:00:13,430 --> 00:00:19,460
We want to happen as early as possible in the project because we know what happens if you miss identifying

4
00:00:19,460 --> 00:00:22,210
a stakeholder and you have to find them later.

5
00:00:22,280 --> 00:00:23,870
They're not going to be very happy.

6
00:00:23,870 --> 00:00:28,880
They may have new requirements and that can have a big ripple effect through the project.

7
00:00:29,060 --> 00:00:34,850
So stakeholder identification we try to capture and complete this process as early as possible in the

8
00:00:34,850 --> 00:00:38,090
project when we do stakeholder identification.

9
00:00:38,090 --> 00:00:45,440
We want to identify the groups and the individuals that are affected by our project and the groups and

10
00:00:45,440 --> 00:00:47,860
individuals that can affect our project.

11
00:00:48,080 --> 00:00:51,130
So we want to document that stakeholder information.

12
00:00:51,260 --> 00:00:54,200
So we think about the public at large.

13
00:00:54,230 --> 00:00:57,370
You think about the people actually paying for the project.

14
00:00:57,560 --> 00:00:58,810
Think about your project team.

15
00:00:58,820 --> 00:01:00,100
They are stakeholders.

16
00:01:00,300 --> 00:01:05,570
And then you think about the recipient and how they will use what you're creating that they are stakeholders

17
00:01:05,570 --> 00:01:06,830
as well.

18
00:01:06,830 --> 00:01:12,520
So we identify stakeholders and then we document the information in the stakeholder register.

19
00:01:12,540 --> 00:01:17,230
We've seen the stakeholder register pop up many times through our course.

20
00:01:17,300 --> 00:01:25,010
Let's look at the Ito's for identifying stakeholders or inputs the project charter the business documents

21
00:01:25,010 --> 00:01:31,700
like the business case and the benefits management plan the project management plan communications management

22
00:01:31,700 --> 00:01:41,090
plan stakeholder engagement plan and project documents change log the issue log requirements documentation

23
00:01:41,660 --> 00:01:48,740
any agreements or contracts or relationships and E.F and opaque tools and techniques you need expert

24
00:01:48,740 --> 00:01:49,470
judgment.

25
00:01:49,520 --> 00:01:55,970
You're going to do some data gathering late Question year surveys brainstorming data analysis you're

26
00:01:55,970 --> 00:01:57,770
going to study the information.

27
00:01:57,770 --> 00:02:04,220
So you have document analysis but also stakeholder analysis really understanding stakeholders concerns

28
00:02:04,220 --> 00:02:06,650
and interest in the project.

29
00:02:06,650 --> 00:02:12,970
We'll do some data representation there is a few charts that you want to know with stakeholder engagement.

30
00:02:12,980 --> 00:02:15,640
We'll do some stakeholder mapping and representation.

31
00:02:15,680 --> 00:02:20,300
Those are some of those charts as well and meetings are going to go out and meet with stakeholders and

32
00:02:20,300 --> 00:02:26,030
you'll meet with him on a regular basis the outputs of identifying stakeholders will be the stakeholder

33
00:02:26,030 --> 00:02:28,420
register that's the primary output.

34
00:02:28,730 --> 00:02:34,630
You might have change requestors you identify stakeholders You may also identify requirements.

35
00:02:34,640 --> 00:02:42,860
The PM plan updates requirements management plan updates communications management plan updates the

36
00:02:42,860 --> 00:02:47,230
risk plan can be updated and your stakeholder engagement plan could be updated.

37
00:02:47,360 --> 00:02:52,220
Remember this is an iterative activity so we don't have the plan right now.

38
00:02:52,310 --> 00:02:54,590
But as we go into planning we'll create it.

39
00:02:54,650 --> 00:02:55,790
But this is iterative.

40
00:02:55,820 --> 00:02:57,980
We may have updates to the plan.

41
00:02:58,640 --> 00:03:03,860
You might also have some updates to some project documents the assumption log the issue log and the

42
00:03:03,860 --> 00:03:07,050
risk register could all be updated.

43
00:03:07,070 --> 00:03:09,330
So who are stakeholders.

44
00:03:09,410 --> 00:03:14,570
Well you know the stakeholders are the people and the organization that are involved in your project.

45
00:03:14,570 --> 00:03:18,060
They can be affected positively or negatively.

46
00:03:18,100 --> 00:03:23,070
It's anyone or any group that has influence over the project.

47
00:03:23,270 --> 00:03:27,340
So some tricky things can happen here you think about the Inspector.

48
00:03:27,380 --> 00:03:33,950
You think about the people in the procurement department or whatever framework you have or workflow

49
00:03:34,010 --> 00:03:37,190
that you have to get work done in your organization.

50
00:03:37,340 --> 00:03:38,810
Those people are stakeholders.

51
00:03:38,810 --> 00:03:41,910
They can have an influence over your project.

52
00:03:42,110 --> 00:03:47,000
So be careful with all stakeholders not just the team and not just customers.

53
00:03:47,000 --> 00:03:53,320
They can be people that are kind of on the fringe of the project but they certainly influence the project.

54
00:03:55,250 --> 00:04:01,160
So we look for people that are affected who will this project affect what people can exert influence

55
00:04:01,160 --> 00:04:02,850
like the inspectors.

56
00:04:02,930 --> 00:04:06,340
I try to identify stakeholders as early as possible.

57
00:04:06,440 --> 00:04:10,060
You don't want to miss people when you go out and identify stakeholders.

58
00:04:10,070 --> 00:04:16,310
This helps to create a stakeholder management strategy or a stakeholder engagement strategy.

59
00:04:16,310 --> 00:04:22,370
So how we engage stakeholders and keep them excited keep them bought into the project and to keep moving

60
00:04:22,520 --> 00:04:24,830
towards creating the solution.

61
00:04:25,250 --> 00:04:31,310
We want to classify stakeholders according to their interest in the project their influence and their

62
00:04:31,310 --> 00:04:32,410
involvement.

63
00:04:32,690 --> 00:04:35,010
So what's the level of interest.

64
00:04:35,060 --> 00:04:40,160
What's their level of influence or high interest high influence and high involvement.

65
00:04:40,160 --> 00:04:41,990
That's a very important stakeholder.

66
00:04:42,110 --> 00:04:49,670
So people have varying levels here of interest influence and involvement data gathering is one of our

67
00:04:49,670 --> 00:04:51,050
tools and techniques.

68
00:04:51,080 --> 00:04:55,110
So you have a lot of stakeholders that you need to talk to and engage.

69
00:04:55,280 --> 00:04:58,450
So it's not always feasible to have a one on one interview.

70
00:04:58,580 --> 00:05:03,030
So maybe we do some question years and surveys to help identify.

71
00:05:03,080 --> 00:05:04,960
Are you a stakeholder or not.

72
00:05:05,570 --> 00:05:10,710
Brainstorming maybe we can get our project team together and we can do some brainstorming.

73
00:05:10,880 --> 00:05:16,820
Or there's another variation of this called Brain writing where I take an opportunity to brainstorm

74
00:05:16,820 --> 00:05:22,240
in private and then we come to the meeting with all of our brainstorming ideas ready to go.

75
00:05:22,250 --> 00:05:28,310
So data gathering techniques to identify stakeholders is a key tool and technique you should know.

76
00:05:28,700 --> 00:05:29,790
All right great job.

77
00:05:29,900 --> 00:05:31,550
I'll see you in the next lecture.
