Agile Software Project Management

Traditional Project Management vs. Agile Project Management

Differences in the roles of project management

What are the differences between the tasks of conventional project managers and the role models in agile project management? The tasks were divided thematically between the product owner and the scrum master.

Product Owner

The Product Owners are responsible for ensuring the ROI (Return on Investment) of the project and making sure that the value of a product is always given. Therefore, they represent the interface between our development team and our customers, and are also the primary point of contact for all stakeholders. It is important that the requirements defined by them are correctly interpreted by the team and that the appropriate product is developed to meet the defined needs of our customers. So, based on the requirements brought to them, they distribute the specific work orders to our team, which is primarily self-organized. Another important part of a Product Owner’s job is to define the right order of delivered functionalities. Most importantly, our Product Owners create a vision in projects, ensuring that everyone involved is clear about what and for what purpose a product is being developed.

Scrum Master

In Scrum (agile framework), a Scrum Master primarily takes on the role of a team coach or trainer. Scrum masters are not seen as disciplinary leaders, but rather should be mentors for the team. They are responsible for removing barriers and enabling the team to work efficiently. They also ensure that everyone in the team understands and properly implements agile practices. Team meetings are facilitated by our Scrum Masters and in case of conflicts, they are the central point of contact for all our team members. Subsequently, they try to solve conflicts together and thus our Scrum Masters try to create transparency in the team.

“Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”

Principle #1 – Ensure early and continuous customer satisfaction

“Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.”

Principle #2 – Changes are something good

“Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.”

Principle #3 – Deliver working software frequently

“Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done.”

Principle #4 - Self-organization

“Working software is the primary measure of progress.”

Principle #5 - How agile teams measure their progress

“Continuous attention to technical excellence and good design enhances agility.”

Principle #6 - Continuous transparency and learning

“Simplicity - the art of maximizing the amount of work not done - is essential.”

Principle #7 - Simplicity