At Neoteric, it is an unwritten rule that all of us share our knowledge with those who want to learn. That’s why we’re always happy to take part in initiatives related to promoting agile project management. This month, together with my friend Bartek, we gave a lecture and a short workshop about Scrum.
Who are we?
Project Management is our profession and passion. We are enthusiasts of agile methodologies and innovative technologies. Our day begins with conversations with Australia and Singapore and ends with calls with the United States and Canada (you can read about the challenges of managing projects in different time zones in my previous article). We manage projects related to the creation of web and mobile applications for clients from various parts of the world and with diverse business profiles.
What is Scrum and why is it so easy to fall in love with it?
Scrum is a framework. In the IT area, it is a well-known way of working. Scrum gives us some tips on how to manage projects.
According to the Scrum Guide: “Scrum is a framework for developing, delivering, and sustaining complex products. This Guide contains the definition of Scrum. This definition consists of Scrum’s roles, events, artifacts, and the rules that bind them together. Ken Schwaber and Jeff Sutherland developed Scrum; the Scrum Guide is written and provided by them. Together, they stand behind the Scrum Guide.”
A very important part to understanding Scrum is getting to know the roles. The Scrum Team consists of Product Owner, Development Team, and Scrum Master.
It’s the only person responsible for managing Product Backlog, an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. The concept of managing Product Backlog includes:
- organizing the order of elements of the Product Backlog in a way that best achieves the goals and missions set up,
- optimizing the value of work performed by the Development Team,
- ensuring that the Product Backlog is available, transparent and clear to everyone, and also describes what the Scrum Team will be dealing with in the next step,
- ensuring that the Development Team understands the elements of the Product Backlog in the required degree.