
Agile Project Management – Part 1
What is Agile?
While traditional project management is still widely used, the benefits of an Agile approach to running a project are becoming more and more recognized. Where Agile has a distinct advantage over classic project management is the development of new products. There is always uncertainty when taking an idea from concept through to a delivered reality. This is especially true when it is something as intangible as a piece of software. The one certainty is that there will be changes required along the journey, and this is what Agile recognizes. A classic project has detailed planning before the project is started, and the successful project will reach completion with the minimum of change in scope and direction.
An Agile project is started with the minimum of planning. The project will accept changes, as long as they are critical to delivering a viable product. The project must also be judged as successful by the level of customer satisfaction. And all this is achieved without a project manager.
Does this mean that Agile Projects have no Project Management?
On the contrary, Agile projects are very tightly managed. Firstly the project and its components and activities are all time-boxed. This enables the team to focus on what has to be done, as the end date is fixed and immutable. The size and capacity of the team are also fixed; the only variable is changed to the product definition. The management of the project and the responsibility for successful delivery is a team effort, where each team member accepts the part they play in project success, thus removing the need for a project manager.
Work is not allocated; a team member selects their next work item by taking it from the sprint backlog or the Kanban board, depending on the Agile framework that is being used. While the project manager plays no part in an Agile project, there are 2 core roles in Scrum that are essential: the Product Owner, who is responsible for the product and all communications external to the project with stakeholders and other parties; and the Scrum Master, who is concerned with the internal communications and project processes.
59 Seconds Training Video
<– Continue Reading –>
Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)
Introductory Offer: Free Course
Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)
What is this course?
This ‘Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)’ provides an in-depth understanding of the Agile Scrum Developer roles and responsibilities
You will explore the Agile Scrum project life-cycle, including how an Agile User Story is created, to how we know when it is ‘done’
This course is aimed at those with or without prior knowledge and experience of the Agile values and principles
During this course you will learn the tools needed to succeed as an Agile Scrum Developer
What will you learn?
You will gain an in-depth understanding of the Agile Scrum Developer roles and responsibilities, and you will be able to
- Fully understand the role of the Agile Scrum Developer
- Understand the roles involved in an Agile project
- Create an effective Product Backlog
- Effectively participate in Scrum Meetings such as the Daily Stand-up, Sprint Review and Retrospective
- Identify the roles involves in the Scrum Team

What topics are covered within this course
You will cover the following topics during this course:
- An Introduction to Agile Project Management (Developer)
- The 12 Agile Principles (Developer)
- Introduction to Scrum (Developer)
- Scrum Project Roles (Developer)
- The Agile Project Life-cycle (Developer)
- Acceptance Criteria and the Prioritised Product Backlog (Developer)
- Initiating an Agile Project (Developer)
- Forming the Scrum Team (Developer)
- Epics and Personas (Developer)
- User Stories and Tasks (Developer)
- Implementation of Scrum (Developer)
- The Daily Scrum (Developer)
- The Product Backlog (Developer)
- Scrum Charts (Developer)
- Review and Retrospective (Developer)
- Validating a Sprint (Developer)
- Retrospective Sprint (Developer)
- Releasing the Product (Developer)
- The Communication Plan (Developer)
- Formal Business Sign-off (Developer)
Our Book Recommendations
We found these books great for finding out more information on Agile Scrum: