Set the Scope for a Successful Project-Prevent Scope Creep
What you'll learn
- 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
- You will learn how to prepare for the Scope Definition Workshop
- You will learn how to run the Scope Definition Workshop
- You will learn how to document the decisions made at the Scope Definition Workshop
Requirements
- Sufficient experience of IT projects to recognise the problems caused by poorly defined scope
- Access to a device capable of running courses on the Udemy site
Description
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!
Who this course is for:
- Project Managers
- Business Analysts
- Technical Analysts
Instructor
- 4.3 Instructor Rating
- 138 Reviews
- 2,371 Students
- 3 Courses
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 confidence, while understanding your limitations. I think you will find working at your own pace liberating and you can contact me during the course if you wish to.
I started my working life as an engineer. I have a BSc in Chemical Engineering from Aston University in Birmingham, England. As a result of my work as an engineering designer, I became interested in computing and eventually I joined IBM as a Systems Engineer, working in pre-sales for customers in the aerospace industry.
Within IBM, I moved to a consultancy group and worked directly for customers as a Business or Technical Analyst for twenty-five years. I served a wide variety of customers from large “blue chip" corporations and government departments to start-ups. I have designed, developed and maintained computer systems, large and small, on a wide variety of platforms.
In my experience of the Information Technology industry, I have found that some skills have been of lasting value. SQL is one such technical skill. Problem solving, some analysis techniques and the so-called "soft skills" are others. All of these improve your ability to communicate with both the business and technical staff make you a more valuable member of a team.
I live in the Republic of Ireland and, when I'm not working for Customers, or writing and supporting courses, I am improving my skill in the Russian language.