Methodology

Methodology

Scrum-like light agile approach items:

• Project Backlog (at the initial start of project)

  1. Define on initial phase before start of project
  2. List of features, functionality and other work required (prioritized based on business value and risk)

• Sprint Planning Meeting (every Monday)

  1. Every Sprint has fixed period of time = 1 week
  2. Team select what it will commit to deliver by the end of the Sprint
  3. Team makes assignment of tasks
  4. Every team players gives estimates for each task (based on story-point approach using fibonacci sequences)

• Sprint Backlog (every Monday)

• Daily Standup (every day)

  1. A short meeting daily to update each other on progress and surface impediments
  2. Strictly time-boxed to 15 minutes
  3. 3 questions
     • what was done since last meeting
     • what will be done by the next meeting
     • any issues, blockers/stoppers, impediments
  4. TeamLead notes all issues/impediments, and afterwards helps to resolve them
  5. This meeting is not for monitoring the team
  6. Via text if you can't be present
     • if you do not feel well today, and going to take day-off - please inform your team

• Sprint Review (Demo) (every Friday)

  1. Performed at the end of Sprint
  2. All come together, and see a demo of what the team has produced

• Sprint Retrospective (30 mins) (every Friday)

  1. Save all notes to wiki/Weekly-retrospective-notes

  2. Start voting of king of current sprint

  3. Create & Send form (anonymously, via Google Forms) to send feedback about TeamLead work

     • What has been done well?
     • What can be improved?

  4. Review the commitment results of Sprint (what have been done, current progress)

  5. TeamLead should share his thought about current week progress

     • Feedback for whole team (at least 5 points)
       • What has been done well?
       • What can be improved?

  6. Brainstorm everything that worked well

  7. Brainstorm areas of improvement

  8. Brainstorm action items to address areas of improvement (how to avoid current issues)

  9. Select action items to implement next sprint and commit to improve

  10. Announce king of current sprint

  11. Current TeamLead choose next TeamLead using random.org by those who applied

Roles

• TeamLead

  • responsible for progress on current week

  • responsible for daily standups

    • proposal: send email invites to team players for auto-reminders

  • responsible for documentation and notes during his week

  • responsible for removing any impediments that surface

  • doesn't manage (direct) the team

Process Control

• Every task must be completely and unambiguously understood (well-done definition)

Definition of Done

• Everyone agrees on the definition of done