head

Dr. W. Brett McKenzie, 210 Gabelli School of Business
E-mail: wmckenzie@rwu.edu Office Telephone: (401) 254-3534

|| Home || Calendar || Syllabus ||

Teams

You will be in teams of three to five people. These teams will be reformed for each project.

Roles: there are only two specified roles, Project Owner and Scrum Master, in the teams. You may specify the other roles, my listing is of functional roles.

  • Project Owner
    You are resposible for making the final decisions about the project - you can image yourself as being the representative of the client. You will "own" the project
  • Scrum Master (can be combined with Project Owner)
    You are responsible for organizing the teams and ensuring the work is completed. Your role is to ensure that impediments are removed. If this means "reserving" computers to work on, then you should find a means to do so.
  • Documentarian
    You are responsible for preparing the documentation for the team - this includes the planning documents and the user instructions
  • Test Master (Can be combined with Documentarian)
    You are responsible for defining the test that will determine whether your project meets the requirements.
  • Presenter
    You are responsible for presenting your project to the class.

Function: there are three functions that must be completed by team.

  • Coding
    This is building the actual project - in the databse, for example, it is building the tables, relationships, and controls.
  • Testing
    Your projects should all be built to a test or question. The definition of this test/question precedes the development of the project.
  • Documentation
    There are two aspects. First, the design documents which describe the project. Second, the user or visitor guides.

Process

  • You will describe the project
  • The Project Owner and Scrum Master will develop a "Product Backlog". This is a list of the tasks that the team must complete in the period alotted for the project. This list is built in consultation with the team members.
  • Each project will have a set of design documents. These are living documents that reflect changes as you build the project.
  • Scrum Meetings will be enacted where participants answer the following:
    • What did you do?
    • What will you do next?
    • What is in your way?
  • Sprint Review Meeting where you demonstrate the project at the end of the project period.

 

Reference: http://www.mountaingoatsoftware.com/scrum

foot