Hardware Reference
In-Depth Information
engineering days based on previous sprints (historical base of sprint back-
logs), previous projects (historical base of product backlogs), capacity for
the forthcoming sprint and the relative US complexity required to deliver
the sprint goal. Burndown and Burnup models [37] facilitating the effort
estimate.
- SP2.1 Establish the Budget and Schedule. During pre-game phase initial
milestones (sprint goals), schedule (sprints), constraints and budget are setup
according to the initial product backlog. Additional milestones or budget
may be assigned to the project in each sprint during its planning. Correc-
tive action criteria are identified during retrospective meeting. The Product
Owner is an outstanding figure to implement these practices in a successful
way.
- SP2.2 Identify Project Risks. In Scrum risks are captured as impediments
(list of impediments). Their identification is not carried out in the initial
plan or in a systematic manner. But this practice is partially satisfied in
an iterative way, during daily meetings, and impediments are revised in
retrospective meeting. The ScrumMaster is the outstanding figure in this
identification process.
- SP2.3 Plan for Data Management. Any data generated by the project is
stored in public folders or white-boards available to everyone [28], but there
is no formal data management plan or procedure to collect this data [26].
Privacy and security are another weaknesses.
- SP2.4 Plan for Project Resources. During pre-game phase the stang re-
quirements and equipment list are defined. As the result the Scrum Team is
established. During the sprints execution, the ScrumMaster is in charge of
providing new resources it should be necessary.
- SP2.5 Plan for Needed Knowledge and Skills. Knowledge and skills needs
are identified during pre-game phase, however the definition of mechanisms
to provide knowledge and skills not found in the organization are considered
as impediments and resolved during daily and retrospectives meetings.
- SP2.6 Plan Stakeholder Involvement. Scrum defines roles, responsibilities,
and involvement of the stakeholders at the beginning and end or each sprint.
This involvement is monitored by the ScrumMaster who is in charge of as-
suring the fulfilling of Scrum practices by all stakeholders.
- SP2.7 Establish the Project Plan. To start a Scrum project a vision and a
product backlog are the basis for the project plan [28].
- SP3.1 Review Plans That Affect the Project. Plans reviews are carried out
during planning and retrospectives meetings.
- SP3.2 Reconcile Work and Resource Levels. Work reconciliation occurs dur-
ing planning meetings because product backlog is dynamic, so new estima-
tions or schedules are possible.
- SP3.3 Obtain Plan Commitment. The commitment is obtained in an iterative
way during face to face planning meetings in which stakeholders are involved.
Search WWH ::




Custom Search