The successful completion of any project is always tightly related to the quality of the project management activities. Nowadays, in the software industry, Agile, Scrum and Scrum variations are the most popular project management approaches used worldwide. The reasons for these choices are many and ultimately they are all about their proven efficiency in the software development lifecycle management.
Being Agile means being flexible to adapt to changing scenarios, while being able to deliver high-quality software solutions.
This is why we also embrace Agile methodologies in most of our projects. Many times it is our customers and partners who ask us to use Agile methodologies (Scrum, Kanban) from the inception of the project. When the choice is left to our engineers, we carefully analyze the project specifics, and we propose a project management methodology based on Scrum or Kanban which best fits the specific project needs and context.
For most of our projects we do Scrum following these general rules:
- The Product Owner is a client representative
- The Scrum master role is usually fulfilled by the Arnia’s team technical lead role
- Each Sprint duration is usually two weeks long
- Our daily Scrum stand-up meetings are set to max. 2 min. per team member
- Within each Sprint we have:
- A Grooming meeting, which is organized during the last week of the Sprint, in preparation to the Planning meeting.
- A Planning meeting, usually taking place in the first day of the Sprint. The immediate result of this meeting is the Sprint backlog.
- A Retrospective meeting, usually taking place in the last Thursday or Friday of the Sprint. The result is an action plan to improve, with clear responsibilities assigned.
- In the last day of the Sprint, we prepare the Sprint status report, which is sent to every party with interest in the project lifecycle.
- The Product backlog will be maintained in an online tool (such as Jira Atlassian)
- Weekly (or whenever needed) Sprint statuses are shared via e-mails and/or via direct communication (live meetings) with the project stakeholders
We always try to emphasis during the project lifecycle the usage of those methods and techniques which best fit the Agile methodology/concepts:
- Prototyping and frequent customer validation
- Continuous integration
- Pair programming
- Code review
- Test Driven Development
- Code refactoring
As a general rule, the Scrum project management processes will be minimized as much as possible – we target to avoid project oversizing and unnecessary/low-value procedures and activities.