My 7 sacred rules for our agile business development in SCRUM format

Generally speaking, we can summarise that the more than 20 weeks we have been working in SCRUM have been a great success. There are always steps backwards, which shows that we need to add nuances to improve our way of working.

That is why today we need to specify

We never execute tasks spontaneously: All tasks are planned in advance. If the task does not exist in the backlog or in the sprint, it is not relevant. The priority is in the tasks planned for each sprint. You cannot do anything other than complete these tasks.

The productivity of the team is more cayman islands phone number library important than your own: You can never sacrifice time from your colleagues to complete a task faster. Other people’s time is more sacred than your own. When a task requires collaboration, you have to coordinate and plan to find a common space for everyone.

phone number library

We plan weeks and days in advance

It is not possible to execute one Live chat på et nettsted kan fungere task after the next. You have to evaluate priorities and dependencies. The order of the tasks matters to achieve the highest level of productivity. The day begins by planning the same day. The day ends by planning the next one. The same applies at the weekly level.
The productivity of the team is more important than your own: You can never sacrifice time from your colleagues to complete a task faster. Other people’s ao lists time is more sacred than your own. When a task requires collaboration, you have to coordinate and plan to find a common space for everyone.

Documentation is key:

There can be no excuses for not documenting the progress of work, decisions, meetings, etc. Memory is fragile, but Confluence pages will persist just like Sharepoint files.
Promises must be kept:

After 20 weeks we must be able to estimate tasks with at least 80% accuracy. Completing all the tasks in the sprint is not optional but mandatory. If we don’t get there, the team deserves a good explanation as to why we weren’t able to reach our goal.
Communication in Jira tickets and not outside of them: To create total transparency for everyone about the status of a task, you have to communicate through the tasks. Also, if there is no progress, you have to document it there. That’s what comment fields are for.

Small improvements every week:

the only tasks that are not tasks in Jira are those that can be executed in a matter of 5 minutes. We will improve every week but without creating additional work.

This is the last measure we have started this week.
We have a long way to go. As I told my brother yesterday, as an organization and team we have gone from level 4 to level 6-7. There is a long way to go but the progress has been remarkable.

Scroll to Top