Homec4science
Diffusion invenio-infoscience (master) Browse

R3600/docs/processes/sprinting.rst
8ef07c807e51master

Last Change
Raw File

sprinting.rst
View Options

.. This file is part of Invenio
Copyright (C) 2015, 2016 CERN.
Invenio is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of the
License, or (at your option) any later version.
Invenio is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.
You should have received a copy of the GNU General Public License
along with Invenio; if not, write to the Free Software Foundation, Inc.,
59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
===========
Sprinting
===========
::
Ah, unfinished issues!
All that remains
Of the Scrum Master dreams.
—-after Matsuo Basho (1644-1694)
Sprinting principles
====================
.. _before-planning-sprint-do-your-homework:
1. **Before planning a sprint, do your homework.** Start by drafting initial
thoughts about high-level requirements and use cases in an RFC. Be specific.
i. About
ii. Use cases
iii. Mock-up screenshots
iv. High-level architecture
v. High-level API
.. _discuss-with-various-invenio-services-and-experts:
2. **Discuss with various Invenio services and experts.** Check for other
similar use cases and synergies. Use the community. Seek expert opinions.
.. _establish-a-cross-service-team:
3. **Establish a cross-service team.** "Alone we can do so little; together we
can do so much." --Helen Keller
.. _start-with-a-kick-off-meeting:
4. **Start with a kick-off meeting.** Invite all sprint team members to kick off
the sprint and plan its details collectively. Invite related technology
experts to provide input to estimated tasks. Invite related service managers
to help making sure the use cases were well understood.
.. _establish-a-backlog-of-tasks:
5. **Establish a backlog of tasks.** List everything that needs to be done. Keep
it short. Use GitHub "Sprint-Foo" labels or milestones.
.. _keep-it-manageable:
6. **Keep it manageable.** Plan no more than a two-week sprint. Break up longer
sprints into manageable two-week chunks. Beware of attention span.
Prioritise.
.. _act:
7. **Act.** Trying our best to finish all tasks in time? "No. Try not. Do. Or do
not. There is no try." (--Master Yoda)
.. _hold-very-short-daily-stand-up-meetings:
8. **Hold very short daily stand-up meetings.** What has everyone done since
yesterday? Is anyone blocked by anything? What is everyone going to do next?
.. _once-over-review-achievements:
9. **Once over, review achievements.** Did everything go as planned? Were you
too optimistic or too pessimistic regarding backlog and time planning? What
have we learned?
.. _finish-by-releasing-packages-and-deploying-features:
10. **Finish by releasing packages and deploying features.** Close sprints by
releasing the software and deploying the features on concerned services ---
production or sandbox.
c4science · Help