training-guides/doc/upstream-training/source/20-training-agile-for-contributors.rst
Pranav Salunke f1e4bfeca8 Porting presentations to Sphinx/Hieroglyph
modifided tox.ini and requirements.txt to install
hieroglyph, added some changes in the styles
of the individual .rst files to support hiero

Change-Id: Id2674e593857470cf4efa0706a4fbda33813f374
2015-03-26 14:33:38 +01:00

1.9 KiB

Lego applied to Free Software contributions


Agile manifesto

  • Customer satisfaction by rapid delivery of useful software
  • Welcome changing requirements, even late in development
  • Working software is delivered frequently (weeks rather than months)
  • Working software is the principal measure of progress
  • Sustainable development, able to maintain a constant pace
  • Close, daily co-operation between business people and developers
  • Face-to-face conversation is the best form of communication (co-location)
  • Projects are built around motivated individuals, who should be trusted
  • Continuous attention to technical excellence and good design
  • Simplicity- The art of maximizing the amount of work not done - is essential
  • Self-organizing teams
  • Regular adaptation to changing circumstances

Applying agile

  • Finding Roles : Product Owner, Scrum Master and Team Member
  • No person has an ideal role
  • The role is hidden
  • Discovering the roles is an ongoing work

Lego town

  • Upstream project : a lego town
  • Company deadline : lego exhibition
  • Epic: become a major contributor and demonstrate the company skills during the exhibition

Upstream

  • Board : 1
  • Technical committee : 1
  • PTL : 1
  • Core : 5

Company

  • CEO : 1
  • Product owner : 1
  • Scrum Master : 1
  • Team members : 5

Free Software contributors

  • Distracted : 1
  • Controversial : 1
  • Agreeable : X

Epic

  • Discuss with the product owner
  • Write user stories

Sprint

  • 5 minutes planning
  • 15 minutes building
  • 5 minutes review

image


Communication


Diplomacy


Time to play with Legos