0002: Start with High-Level Requirements

[@shelbytownsend3511]

Good video, can you do an example of the steps you need to gather high-level requirements? It would be great to see a case study of you showing us the process and list them out in a use case and user stories.

[@LeelooZA]

Great video and well explained, thanks!

[@khadijatbadmus4883]

Thank you

[@7861varis]

Excellent video! Not sure why your channel/videos aren't getting much traction. Nonetheless, I found your content to be very helpful. Thanks!

[@peterazubuike8078]

you are very good

[@peterazubuike8078]

can you explain funtional requirement ,non functional requirement ,Epic and feauture

[@beatsbreedercrooze999]

how does th high level requirements differ from the deliverables, should we include them both when typing out the project charter

[@prugresustrategiccoaching3890]

My apologies for the late reply, I didn’t seem to get a notification from KZbin of your comment. To answer your question, deliverables are key components of a project that must be developed/created/completed in order to meet the high level requirements. HLR’s are what the final result of the project seek to satisfy. A good example could be the building of a house: One HLR could be a “2-car garage” - and some deliverables for this requirement would be installation of the automatic garage door, garage lighting, and maybe concrete floors. Hopefully this helps a little bit more.

[@peterazubuike8078]

hello bro how can we connect please

[@beatsbreedercrooze999]

im sorry I commented too early. you are actually killing it

[@prugresustrategiccoaching3890]

Thank you!

[@beatsbreedercrooze999]

you keep losing me, especially on explaining what SHOULDN"T be the case