A. Technology.
B. Client or stakeholder.
C. Personnel.
Or D. Developer?
The correct answer is B.
This issue is a client risk.
Basically, there's a possibility that your project's success
is jeopardized by your client's action.
Since Steven's work won't be affected, this isn't a personnel risk.
Let's hear about some common and
recurring risks that could effect the success of a product.
[MUSIC]
>> Well on early stage, startups in particular,
and with some IT projects, a lot of it is funding.
People grossly underestimate how much effort and skill is required and so
there's often not enough funding.
So when money gets tight, it just affects everything.
People's morale gets lower.
People are worried about their jobs and things like that.
So, it can be a real killer.
So a lot of great ideas and
projects just die on the vine because people didn't cost them properly.
Another thing is personnel.
Particularly, again, early-stage startups or
early projects at a company that haven't been done before.
You sometimes you have to deal with the people you have.
And if you don't have the right type of skill to go from point A to point B,
you can end up with a lot of problems and people start to blame each other.
I thought you could deliver this?
People might have bit off a bit more than they can chew.
So you need to make sure that you're staffing things correctly and
have the right mix of skills and the right roles.
And then another big one that I see everywhere is a lack of planning.
So the agile methods are great for lightweight,
lots of customer interaction, lots of testing, lots of good ideas, but
people get the feeling that we're gonna move really fast and we don't wanna plan.
Well, it's not that you don't plan.
You need to have a plan that's appropriate.
That gives you some flexibility to still be agile congruent.
But most of what I see is a lack of planning.
So, technical teams will think that if they follow a particular process, or
they use particular software solutions, that it'll just work.
Well, it doesn't work.
So a lack of planning is an absolute killer.
100% of the projects that I see fail, they all have poor planning in common.
And the projects that do succeed, they have a plan.
Now the plan may change a lot, but
there's something that comes out of thinking about things, writing it down,
communicating that really helps get people aligned and moving in the right direction.