PROJECT MANAGEMENT COURSE – 1. Waterfall or Traditional Project Management Course and 2. Agile Project Management Course
PROJECT MANAGEMENT COURSE
What you’ll learn
- Students will gain knowledge about PROJECT MANAGEMENT COURSE.
- Students will learn Waterfall or Traditional Project Management Course – Fundamentals.
- Students will learn Agile Project Management Course – Fundamentals.
- Students will learn Basic Management Skills.
Course Content
- Introduction –> 11 lectures • 1hr 36min.
Requirements
PROJECT MANAGEMENT COURSE
THERE ARE 2 TYPES OF PROJECT MANAGEMENT COURSES or METHODS ARE THERE
1. WATERFALL OR TRADITIONAL PROJECT MANAGEMENT
2. AGILE PROJECT MANAGEMENT
WE WILL LEARN ABOUT
1. WATERFALL OR TRADITIONAL PROJECT MANAGEMENT includes 5 Chapters
Chapter – 1 : PROJECT MANAGEMENT COURSE – INTRODUCTION
Chapter – 2 : Project Initiation
Chapter – 3 : Project Planning
Chapter – 4 : Project Execusion
Chapter – 5 : Project Closure
2. AGILE PROJECT MANAGEMENT includes 6 Chapters
Chapter – 1 : AGILE PROJECT MANAGEMENT COURSE – INTRODUCTION
Chapter – 2 : AGILE PROJECT MANAGEMENT COURSE
Chapter – 3 : AGILE PROJECT MANAGEMENT COURSE
Chapter – 4 : AGILE PROJECT MANAGEMENT COURSE
Chapter – 5 : AGILE PROJECT MANAGEMENT COURSE
PROJECT MANAGEMENT METHODOLOGIES
The Waterfall project management – The sequential or linear order of phases
The Agile project management – Agiles iterative approach enables a project to
move quickly, as well as making it adaptive to change.
Agile is about delivering a value in a world with high degrees of uncertainty,
risk and competition.
4 values
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to a change over following a plan
12 principles
1. Our highest priority to satisfy the customer through the early and continuous delivery of valuable Software.
2. Welcome changing requirements, even late in development. Agile processes harness change of the customer’s competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project
5. Build projects around motivational individuals. Give them the environment and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face to face conversation
7. Working software is the primary measure of progress
8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely
9. Continuous attention to technical excellence and good design enhances agility
10. Simplicity- the art of maximizing the amount of work not done – is essential
11. The best architectures, requirements, and designs emerge from self-organizing teams
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly