Management - Do you use XP/Scrum wisely?

Last updated by Nick Curran [SSW] 4 months ago.See history

This rule has been archived

Scrum is a big concept which we try to use here. I don't adhere to every idea, but there are some very practical rules I follow which improves the way we develop on large projects:

Figure: You need to check up on your developers every 2 weeks. Then you'll never be fooled!

  1. Sprint Contracts/Releases - Never set a deadline more than 3 weeks from the previous deadline. Deliverables become a lot easier to manage and meet when they're small. Read more about Sprint Contracts
  2. Unit Tests - Write tests before you write code. Unit Tests become a way of life and although they're expensive at the beginning, they pay off during the course of the project. To find out more about Unit Tests see Rules To Better Unit Tests and for unit tests in the GUI of SSW Code Auditor please go to Rules to Better Code.
  3. Metaphors/User Stories - client's description of a task. Aim to take down the main points
  4. Validation Tests - To find out more about Validation Tests see Rules To Better Website Development.
  5. The 2 key reports

    • Burndown
    • Stories Overview

Here are the rules we don't agree with:

  1. Physical Cards - emails are much better
  2. Pair Programming:

    • XP says 2 people at one PC - we have two developers on their own PC's sitting next to each other.
    • We fix production code in pairs. 'Too Expensive' some say. Yes it's pricey, but it's better quality.
We open source. Powered by GitHub