Learn to define project scope effectively without extensive analysis, reducing scope creep and ensuring project success.
This course teaches you how to define the scope of a project easily and effectively, focusing on preventing scope creep. You'll learn straightforward techniques to set clear project boundaries without diving into heavy analysis, making life easier for everyone involved.
“A clear scope makes for a sound project.” This course shows you how to define scope without performing the analysis.
I have seen the start of a lot of projects! Everyone wants to get a project off to a good start, but Analysis and Requirements projects are notoriously difficult to define. This course teaches a technique I have used to define the boundaries of all sorts of things. I've used it as an individual, with a team and with larger groups. I have found it useful. I think you will too.
You will have heard Project Managers complain about “Scope Creep”, Scope creep is when the “To-Do list” keeps growing, especially when it grows faster than we are completing the tasks. Projects work better when: we know what we need to achieve, the scope is fixed, we are not being given extra things to do and the Project Manager and team are not constantly having argue against “things being added”. A clear project scope is one way of combating scope creep.
An analysis project may not start with clear boundaries. If “A clear scope makes for a sound project”, how do we define that scope without performing the analysis? This course shows you how to do just that!
By the end of the course, you will have learned how to run a workshop to define the scope of an Analysis project.
You will learn how to define scope, based on things you know already
You will learn how to use this technique to obtain agreement from the project stakeholders
5 Lectures
7 Lectures
4 Lectures
I'm Tom Gillies and I have been a Business and Technical Analyst in the Information Technology industry for the past thirty years. My courses are based on my real-world experiences. I am teaching as I wish I had been taught. My objective is to give you enough knowledge to make you reasonably self-sufficient, and enough experience to give you reasonable...
The course is well done and follows sound instructional lecture principles: tell them what you're going to tell them, tell them, then tell them what you've told them. Things are broken down into bite size pieces and there is homework with debrief exercises to try out some of the skills. There are quizzes that review basic content. The instructor makes himself available and has a Facebook group for additional ideas.
The challenge I found was transference into the work that I do. I scope out elearning projects and there are always many unknowns in our builds. I was hoping to learn how to tackle this a bit more. I did take away some useful information, making the course a worthwhile investment.
Your email address will not be published. Required fields are marked *
Ben H.
I like that the instructor asks for and encourages a lot of participation from the students. The ideas presented seem to be solid ideas which have been tried and tested in real world scenarios. I get the sense that there is a great deal of experience that is being drawn from when explaining the material.
My complaint is that I still have too many questions after completing the course. Now that I'm done with the course I'm still wondering what to do regarding how to set the scope for a successful project. I would also like to see that the instructor speaks to the information being displayed in the slides. In many cases there are bullet points displayed which have no mention in the spoken part of the lecture.