CS312 - Spring 2012 - Class 13

  • administration
       - sign up for tech talks!

  • git
       - for now, we'll use github
          - it's free
          - it's robust
          - it's easy to use (and has good documentation)
       - I've posted with today's notes a short tutorial on how to set things up and the basic commands

  • development
       - should be generally be working generally in pairs (we'll talk more about pair programming soon)
       - use Git
          - commit regularly
          - get used to resolving conflicts
          - if possible, try and work on separate parts of the code to avoid conflicts (sometimes this is inevitable)

  • scrum master's role
       - make sure people in the group are following the scrum process
       - sprint planning should include:
          - difficulty assignment
          - user story selection
       - sprint stand-up
          - keep the meeting short (if an issue comes up that needs to be discussed, help table the issue for later)
       - spring retrospective
          - lead the discuss
       - the scrum master does NOT
          - act as the team leader
          - have priority over any team member with respect to who does what outside the scrum process

  • project planning
       - solidify backlog
          - put all your user stories in it
          - if any user stories are too big (or too vague) try and break them into smaller ones
          - make sure the user stories are prioritized appropriately
          - if you want to work on something, it needs to be in the backlog!
       - decide on a scrum master!
       - story pointing
          - decide how you want to score the difficulty
          - assign scores for all of your user stories
       - decide how much you're going to tackle for the first sprint
          - it's about 2 weeks of work
          - remember, things often take longer than you think
          - people are going to be a bit slower this first sprint since everyone is getting up to speed
       - decide who is going to be working on what to start with
          - ideally, you'll be working in pairs, though sometimes it makes sense to work individually
          - this can change over the sprint, but you people need to know what they'll be working on for at least the next couple of days
       - set a meeting time for your first standup for sometime this weekend
          - the stand-up should be no more than 15 min.
          - in the stand-up you should discuss
             - what you accomplished since Thursday
             - anything blocking you from moving forward
             - setup any follow-up meetings/discussions
          - don't forget to start updating your personal stand-up logs

  • other things to do
       - please setup a team web page
          - put the team members up there
          - put a short description of the project
          - keep an up to date version of the product backlog here
             - if it's a shared spreadsheet or something like that a link is fine
          - link to the GitHub repository
       - git
          - everyone on the team needs to signup for GitHub
          - someone needs to setup the repository on Git
    •