project schedule our workflow
nvii-media GmbH relies on SCRUM project management for project management. The following tools are used depending on the customer's requirements, scope of the project. The focus is on project management, customer communication and documentation.
Escalation levels, milestones are defined individually.
Deployment, CMS updates, and general site changes
We rely on versioning and ACComplishment, PRDS system separation by simple staging to publish progress on web projects.
The following tools are used here.
The product owner creates a list of requirements - the product backlog - on the basis of usage descriptions. The order of the entries also defines their priority. All project participants contribute to its content.
This happens not only at the beginning of a development and also not only at certain times, but continuously. As soon as change requests or new requirements occur, these are set. This basic openness to accepting changes continually and not to regard them as an obstacle but as opportunities leads to a high flexibility in the development.
Prioritization is often based on the business value or a risk associated with a requirement. This allows you to quickly react to changing conditions without jeopardizing the project.
Sprint Planning Meeting and Sprint Backlog
The Sprint Planning Meeting takes place at the beginning of a sprint. All project roles will be attended by this meeting. Team and product owner decide about the contents of the next sprint.
The latter explains the most prioritized items (»Items«) of the product backlog and explains their professional use. The team estimates the cost of 'Items'.
From the »Items« of the product backlog, the team will select entries for a sprint according to prioritization and move them to the Sprint Backlog.
As soon as the team and the product owner agree to the sprint backlog in the next sprint, the sprint target is defined.
Then, the team adds the Sprint Backlog »Items« to a conversion plan, most of them concrete development activities.
Then start the sprint. The requirements of the Sprint Backlog are not changeable during a sprint for stability reasons.
The Impediment List
Once the first sprint is started, each team member can set the so-called impediments (blockers) into a list. Each team member, as soon as a blocker for the realization of a task has resulted, announces it and places it in the list of blockers.
It is the task of the Scrummaster to eliminate these blockers. A blocker can be a frame condition, but it can also wait for an unfinished task. The blocker is communicated to the other team members in the Daily Scrum Meeting and recorded in the Impediment List.
The second table is an example of an impedance list. The columns can, of course, be extended. Maybe one status per line would be interesting if there were not only open blockers in the list.
Daily Scrum Meeting
Once a sprint has begun, the team and the Scrum Master meet daily for the Daily Scrum Meeting. The Daily Scrum Meeting is an informal meeting of a maximum of 15 minutes, which, in order to keep it short, is often held standing. In this meeting, each team member has the task to answer the following three questions
What would I do today to help the development team reach the goal of the sprint? ? Do I see any obstacle that prevents the development team or me from reaching the goal of the sprint?
This meeting is not a comprehensive discussion, but a brief planning meeting of the team to tune what is to be done on this day to reach the sprint goal. This is the job of the Scrum Master.
The main task of the ScrumMaster is to eliminate blockers, but not the control of the team. The team is organizing itself.
The following guidelines apply to the "Daily Scrum":
The meeting will always take place on the same day and at the same time. The meeting is open, everyone can participate, but the actual roles have language rights. The meeting is always limited to a maximum of 15 minutes, regardless of the team size. The participants should be at the meeting. This should help keep the meeting short.
The Sprint Review Meeting / Scrum Retrospective
At the end of each sprint, a "Review Meeting" takes place, in which the team presents the results to the product owner and other stakeholders. At this date everyone can participate and give feedback on the result and its development.