PM040 Introducing the Requirements Document

all right so far we've talked about why it's important to understand the needs of an organization why it's important to document those needs into requirements we're going to be delivering what's called a requirements document it's part of a project management a series of deliverables that come out of projects uh we've talked about business analysis

and why it's important to understand the six Core Concepts right the needs the changes the stakeholders that are involved in it the value those are all sort of Core Concepts those are all going to play into the successful delivery of a project in class and the lectures we talked about project management we talked about it in terms

of you know the constraints we talked about it in terms of the uh uh the life cycle well what I think it's important to to understand is that those learnings are going to be applied to this this uh assignment here so if we look at the uh definition of a project what is a

project we said it's a temporary Endeavor it's undertaken by organizations to create some sort of unique product service or a result and there's some characteristics that we talk about one it's temporary it has a defined beginning and end so I'll say things like a semester is a project right we have a start we have an end

it's clearly defined we all know when the first day of classes we all know when the at last day of classes will be and we also know when our final exam will be well that's temporary as much as maybe uh uh your semesters stress you out they will end right at some point

there is a definitive end uh projects are unique they're not routine in an organization right it is designed to accomplish some sort of singular goal and that goal may change uh and we may never do that again right many organizations that that build a head office think of Apple's headquarters down in uh uh copertino big sort of