Scrum Roles and Preparation Process
It looks like an agile methodology for planning and project management.
allows for an adaptive approach that seeks to improve the nonlinearity of the projects and aims to change management during the process of developing software.
The term derives from the Rugby Scrum and indicates the fray, this is meant to represent the need for a cohesive team that works together so that everyone pulling in the stessa direzione.
Preparation
Introduzione
La preparazione detta anche Sprint 0, serve per mettere, nel più breve tempo possibile, il team in grado di partire con le iterazioni che porteranno alla consegna del prodotto.
La quantità di lavoro da svolgere per iniziare un progetto, ovviamente varia da organizzazione a organizzazione e da progetto a progetto.
In questa fase vengono coinvolti i responsabili del progetto per organizzare i lavori.
Valutazione Economica
Ogni progetto dovrebbe avere una verifica economica, indipendente dal metodologia scelta per consegnarlo.
La prima cosa importante da considerare è that a clear understanding of the value of the project leads to a greater awareness in their choice of priorities, capabilities and delivery times.
This assessment is likely to be an assessment of high level and that could change and then not be accurate.
is why the product backlog items are evaluated on a daily basis.
The relationship between the benefits achieved and the cost will help determine if a project has been useful.
The inaccuracy of the assessments is often highlighted by the iterative nature of Scrum that can assess the actual progress of the various sprint.
This allows you to mitigate risk assessments inaccurate and can not waste time trying to create accurate assessments too.
One advantage often overlooked is the Scurm of checking the feasibility of a project because, after only a Sprint becomes clear that the requirement may be satisfied.
This allows you to stop the project at the beginning rather than at 6 and 12 months.
Project Vision
Like other agile methodologies do not recommend unnecessary documentation.
becomes important, however, that the entire team understands the essence of the project or the product you are trying to accomplish.
Initial Product Backlog
A product backlog is a list of project requirements ordered by priority with an estimate in days.
Evaluations become more precise the higher the priority.
The priority should be assessing the functionality from the economic point of view and as a return of investment.
This list is not static but changes according to changing conditions over time.
This list is composed of functional requirements and nonfunctional requirements.
Their granularity is dependent on the sprint in which they are present in the current year will receive more detailed and specific.
Any idea or requirement can be added to the product backlog.
This makes the product backlog a very useful tool to calm the people, that in some meetings may make demands that cause friction with the project manager, scum in the answer becomes "Great idea, we'll put it on the Product Backlog and prioritise Against the rest of the backlog."
This causes the value of a new request is compared with the actual value of the rest of the project.
Initial Release Plan
The team enters the first sprint and the identifying product backlog enough consentigli from starting work.
The list of product backlog can exit a business case turned into a requirements document or product directly from the owner.
Assemble Team
Once identified the figures needed for the project, you should arrange a meeting with themes, the aim of the project, the backlog of high-level definition of the scrum time.
Logistics
There are a number of logistics activities to prepare before the start of a project.
The place where the team will work is very important, it would be better if you can join the team in the same room to improve communication, otherwise you must use all the technological means such as telephone and video calls to better manage the communication.
Roles
scrum in the figures are divided by those who are directly involved partially involved.
Product Owner
The product owner is responsible for the return of investment the project.
This person is an investor or someone is interested in the project, is responsible for project delivery and investment associated with it.
Usually this figure is an employee of the customer in charge of the project with responsibilities after release.
The product owner must have an understanding prioritize high-level functional requirements, non-functional and creative project.
has to make sure that the capabilities and priorities.
decides the characteristics of the product delivery date and satisfaction.
Unifies Customer requests and other users.
accept or reject the final work can change priorities every
months is responsible for the Roi
Team Members
People who are the team members have different skills that are necessary to transform the requirements into the product.
Often the team is made by the analyst, the designer, the head of QA, developer, responsible for documentation.
At each iteration the team's work product is submitted to the owner and it can decide what happens next.
In a project of the figures are usually highly specialized with regard to security, usability, databases, etc. ...
These figures should be a clearly defined role, if you play a mentoring or guide the development process of a part or not I can get to be part of those involved.
ScrumMaster
There are several ways to interpret the scrum master is to a parent who teaches the team how to manage with the produc car owner.
Scrum master must enforce the rules and create a cohesive group and raising components.
For maximum performance the scrum master has to ensure that activities involving scrum-compliance.
Another task of the scrum master is to remove any internal or external obstacle to the achievement of goals within the sprint.
allow close cooperation between all the roles of the team and removing barriere.
Protegge il team dalle interferenze esterne
Si accerta che il percorso venga seguito
Insegnando al cliente come elevare ROI e conseguire i loro obiettivi.
Migliora l’ingegneria utilizzando strumenti che permettano la riduzione dei tempi di consegna.
Stakeholder
Tutti i consegnatari potenziali per il progetto dovrebbero essere identificati prima possibile e informati dell’avanzamento del progetto.
Il Processo
L’obbiettivo del processo di Scrum è dare i maggiori risultati ogni mese.
Il processo parte con il product owner che definisce una priorità per i product backlog.
Questo permette di avere un insieme di product backlog da analizzare and plan for the sprint planning meeting.
The team began working on the sprint backlog and occurs daily in the daily scrum.
At the end of the sprint is shown in the work product owner and other stakeholders.
The feedback received will be included in the review poduct during the sprint backlog and will be assigned new priorities.
Before addressing the sprint after the team during the Sprint retrospective discuss performance and make necessary improvements.
Team continues with sprints up to have developed a useful product and running for production.
Daily Scrum Meeting
The Daily Scrum meeting is a daily 15-minute held by each team.
During the meeting, each participant updates on the progress of other activities and the obstacles encountered, the scrum master notes for their removal.
These are very useful because they allow you to quickly identify problems and sharing solutions reduce the time spent.
The team is more consolidated because the goals are clarified and reduces misunderstandings.
remain standing during these meetings improves attention.
Some rules that will help the development of this meeting:
- schedule the meeting in the same place at the same time, preferably in the morning so that the team can think what they did yesterday and what you set out to do today.
- All team members are required to attend, if someone can not be present to communicate its progress.
- Members of the team must be quick. The meeting opened predetermined time without exemption.
- Each team member should speak and say what he did yesterday what he will do today and what problems it has encountered.
- During the meeting asked no questions, we are discussing, not wandering. The scrum master is responsible for the way the meeting.
- The goal of the team to communicate and to talk to the scrum master
- spoken one at a time with no other disorders.
- When a team member points out something interesting or requires the assistance of others there may be an immediate response but the discussion must continue outside of the daily scrum.
- who is not directly involved in the project may participate but must not intervene or interfere.
The Sprint The sprint is a period of time that has to last 30 days where the team works to complete the product backlog to produce an increase in product features. A
months in duration can be long enough to be able to produce something meaningful and short enough to support the development process and be able to improve and evaluate.
The objectives and activities are defined in the sprint at the start of each sprint during the sprint planning meeting.
The progress is tracked through the completion of the sprint backlog and sprint graph Burndown.
As for the project there is a vison is important to have a goal (Goal Sprint) for each sprint.
To better manage each Sprint there are some rules to follow:
- During each sprint, the team can ask for help from external sources but must know the objectives and to manage themselves independently. During the Sprint Planning
- are approved the product backlog to be completed and no one outside would modificari. If the sprint
- can not cancel it for the scrum master can arrange a new meeting schedule. This decision should only be taken by the scrum master. The sprintt can be interrupted if the technology is not viable, if external conditions change so much to suffer on the job if the team is disturbed by external factors.
- If the team feels unable to complete the planned product backlog, you can bargain with the product owner for the removal of some or the scrum master can decide to stop the sprint.
- If during the first days of the sprint, we realize that the load is 20% higher than the sprint to be rescheduled and must be reported this anomaly in the Sprint Retrospective.
- If the situation is reversed then it is scheduled to work less, you can enter new activities by consulting the product owner.
- Team members have two responsibilities, participate in the daily scrum meeting and update activity in the sprint backlog, now adding the new features identified in the product backlog.
- If an activity lasts more than a haunting must be decomposed into more granular tasks.
- The team must follow the conventions and the established practices for software development.
Sprint Planning
The purpose of a sprint is to make a list of product backlog in an increase of functionality.
The scrum master, product owner and the team meet to determine what product features the team will be working.
The owner identifies the product features that would have and the team from an estimate of time to understand its feasibility.
sprint planning can be divided into two phases, the first identifies the possible product backlog to be completed in the second and the team defines the architecture and design features and defines the tasks.
- The product owner defines the priorities
- Together we decide which tasks can be completed in a sprint.
- The team obtained all necessary to verify the feasibility.
- The product owner is responsible for trading activities in respect of stakeholders.
- The team takes over only the work you really think you deliver.
- The capacity of the team can be assessed by looking at the previous sprint and the relative complexity of the required activities.
- The product backlog sprint backlog can be divided into
Sprint Review
sprint review provides a check on the progress of the process at the end of each sprint.
On the basis of the checks can be made without the adaptations. At the end
dello Sprint, la squadra presenta l'incremento sul prodotto.
L'amministrazione, i clienti, gli utenti ed il product owner valutano l'incremento delle funzionalità.
Vengono ascoltate le cose andate bene o male durante lo Sprint.
Dopo di che si hanno gli elementi necessari per decidere come procedere con l’avanzamento del progetto.
Durante questa riunione dovrebbe uscire le richieste di miglioramento o l’aggiunta di funzionalità potendo osservare concretamente il prodotto.
Il team aiuta a prendere le decisioni avendo seguito il processo di sviluppo e conoscendo punti forti e deboli del sistema.
Per operare al meglio durante una sprint review:
- La preparazione della sprint review should not take more than an hour.
- not be offered features that are not completed.
- The presentation of the feature should be done in an environment closer to production such as environmental quality management
- Review of Sprint begins with a member of the team that has the objective of Sprint Backlog completed Product and Product Backlog is not completed. The other team members can comment on what went right or wrong during the sprint.
- Once the presentation will be heard the comments of stakeholders.
- The product owner listens for requests and reorganize the priorities for the next sprint.
- The stakeholders can comment and identify features that were not provided or that do not meet the specifications and propose to the new schedule.
- The scrum master is responsible for deciding who will attend the meeting.
- After the meeting, the Scrum Master announces the date and place of next Sprint Review.
Sprint Retrospective meeting
This facilitates the scrum master and team to identify what can be changed to make the next sprint more productive.sprint review looks at "what" the team is building while the sprint retrospective look at the "how" is constructed.
Everything may become interesting topic, as processes, practices, communication, environment, tools.
Scrum is not a rigid methodology, and then the Sprint Retrospective is an important mechanism that allows a team to continually evolve and improve with the duration of a project. To participate in the sprint retrospective
product owner, Scrum master and the team and everyone can suggest improvements.
becomes important in the emergence of this meeting in an open and constructive problems.
often use an outside person to lead the meeting allows the scrum master to participate more actively and is particularly useful if the emotions and relationships in the team are not harmonious they should be.
