Agile Project Management Introduction

  • Why do you need to understand the (Agile) term?

You've heard this term before, haven't you? Well, that's natural because it's used in a series of industries, being perceived as a manner of work. Agile is defined as being able to move quickly and easily. And, as you expect, Agile Software Development Methodology is a buzzword nowadays. According to formal definitions, Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organising, cross-functional teams. The cross-functional team has an important role to play in Agile as it’s supposed to be self-organising away from the traditional teams that are directed and told what to do. You can take a look at a different approach here

Agile Manifesto Principles

Software environment projects greatly differ from non-software environment projects, as you already know. Software projects have many characteristic features which typically aren’t found in other types of projects which focus on client collaboration. If requirements for the projects aren’t known or stable through the lifecycle of the project, then Agile should be implemented. Moreover, this is propounded in the 3rd principle of the Agile Manifesto, which focus on the availability of business and technical staff to work together with the Agile project on a regular basis. Face to face conversation represents a preferred method of communication as supported by the sixth Principle of the Agile Manifesto. Working product/software is to be taken as the measure of success as told in the eighth principle of the Agile Manifesto, which is also suggested by the 11th principle of Agile Manifesto. 

Requirements can be changed frequently for projects where the end result is speculative during the time of project initiation, planning or execution. The entire production methodology is centred on individuals since the teams are self-organising and have more power than traditional project management processes. This role in OpenAgile maps to the Product Owner role who owns the Product backlog in an agile environment.

Agile Project Management Principles

This is what we think that an Agile PM must embody as a mindset

  • Understand your customer
  • Understand the unfair advantage that you can bring into the market for them
  • Bring speed and agility "on the table"
  • Be sure that transparency and visibility is assured
  • Be flexible to change 
  • Delight your customer with a great delivery

Of course, then comes the implicit job description

  • Risk Management

  • Greater productivity

  • Control of the costs

  • Inspect and adapt 

  • Bring the simplicity to the product

  • Be an inspiration for your team

 

summary-learningLearning Summary

chapter-1