Agile Project Management

Module 1: What Is Agile

Module 2: Projects And Projects Management In An Agile World

1. Projects And Project Management In An Agile World Part1 – Historical Information
2. Projects And Project Management In An Agile World Part2 – Organizational Projects
3. Projects And Project Management In An Agile World Part3 – Traditional Projects
4. Projects And Project Management In An Agile World Part4 – Roles
5. Projects And Project Management In An Agile World Part5 – Roles 2

Module 3: Agile and Scrum

1. Agile And Scrum Part1 – In Depth
2. Agile And Scrum Part2 – Major Activities
3. Agile And Scrum Part3 – 3 Questions
4. Agile And Scrum Part4 – Sprints

Module 4: Common Scrum Terminology

1. Common Scrum Terminology-Part1
2. Common Scrum Terminology-Part2

Module 5: Other Iterative Methods

1. Other Iterative Methods

Module 6: Communication Skills In Agile World

1. Communication Skills In Agile World Part1 – Model
2. Communication Skills In Agile World Part2 – Verbal vs. Nonverbal
3. Communication Skills In Agile World Part3 – Learned Patterns
4. Communication Skills In Agile World Part4 – Key Skills
5. Communication Skills In Agile World Part5 – Key Skills
6. Communication Skills In Agile World Part6 – Conflict Resolution
7. Communication Skills In Agile World Part7 – Tuckman’s 5 Stages

Module 7: Using Agile Outside Software Development

1. Using Agile Outside Software Development-Part1
2. Using Agile Outside Software Development-Part2

Module 8: Case Studies Of Transitioning to Agile

1. Case Studies Of Transitioning To Agile-Part1
2. Case Studies Of Transitioning To Agile Part2 – Procurement
3. Case Studies Of Transitioning To Agile Part3 – In an Agile World
4. Case Studies Of Transitioning To Agile Part4 – Measurements

Module 9: Critique Of Agile

1. Critique Of Agile-Part1
2. Critique Of Agile-Part2

Module 10: Review Of Agile

1. Review Of Agile-Part1
2. Review Of Agile-Part2
3. Review Of Agile-Part3
4. Course Conclusion

Agile project management is an iterative approach to managing software development projects that focuses on continuous releases and incorporating customer feedback with every iteration.

Software teams that embrace agile project management methodologies increase their development speed, expand collaboration, and foster the ability to better respond to market trends.

Here is everything you need to know to get started or refine your agile project management practices.

Traditional agile project management can be categorized into two frameworks: scrum and kanban. While scrum is focused on fixed-length project iterations, kanban is focused on continuous releases. Upon completion, the team immediately moves on to the next.

Scrum is a framework for agile project management that uses fixed-length iterations of work, called sprints. There are four ceremonies that bring structure to each sprint.

It all starts with the backlog, or body of work that needs to be done. In scrum, there are two backlogs: one is the product backlog (owned by the product owner) which is a prioritized list of features, and the other is the sprint backlog which is filled by taking issues from the top of the product backlog until the capacity for the next sprint is reached. Scrum teams have unique roles specific to their stake in the process. Typically there’s a scrum master, or champion of the scrum method for the team; the product owner, who’s the voice of the product;

Kanban is a framework for agile project management that matches the work to the team’s capacity. It’s focused on getting things done as fast as possible, giving teams the ability to react to change even faster than scrum.

Project estimating is an extremely important aspect of both kanban and scrum project management. For kanban, many teams set their WIP limit for each state based on their previous experiences and team size. Scrum teams use project estimating to identify how much work can be done in a particular sprint. Many agile teams adopt unique estimating techniques like planning poker, ideal hours, or story points to determine a numeric value for the task at hand. This gives agile teams a point of reference to refer back to during sprint retrospectives, to see how their team performed. Jira Software can be customized to capture your teams’ unique project estimations.