This topic describes how to set up a new project from scratch on a click by click basis. You should consider using the New Project Wizard instead.

Nuts and Bolts of Starting a Project

  • Click the Start a Project link in the green Projects area along the right hand side of the page.
  • fill out the form
    • the summary serves as the title for various reports
    • access control determines who can access this project
    • the code is used as a lookup value so enter something unique yet meaningful
    • keywords should contain some search terms that you would like this project to appear as part of the results
    • provide a brief summary of the project
    • official start date of the project
    • sell your project in the introduction
    • the audience is a description of who this project intends to serve
    • the status describes the current status of the project
    • issues describes what challenges and opportunities that this project is currently facing
    • roadblocks describe any obsticles that are currently getting in the way of this project
    • anything else you want to talk about should go into notes
    • what chat room should people use if they want to discuss this project with you
  • click the Add button
  • click the display link

Adding a Release to a Project

  • click the Releases link
  • click the Add button
  • About Change Control
    • If you want the management decision for this release to be a part of a bigger decision, then select the appropriate change control from the drop down.
    • If you want the management decision for this release to be by itself (recommended).
      • click the new change control link
      • fill out the Change Control screen
      • approval Status should be initial
      • fill in and remember the code
      • click the add button
      • click the Release link in the Recently Visited box
      • select the newly added code in the drop down for the change control
  • fill out the rest of the form
    • the code is used as a lookup value
    • the version identifies the branding term for this release
    • describe this release in the description field
    • EDT is the Estimated Date of Completion
    • the objectives is where you describe the goals of this release
    • the scope is where you place high-level limitations on what requirements can go into this release
  • click the Add button

Starting a Team

  • click the Start a Team link in the blue Teams area along the right hand side of the page
  • fill out the form
    • since you are creating this, you are the team lead
    • the code is used as a lookup value
    • keywords should contain some search terms that you would like this team to appear as part of the results
    • what is the name of the team
    • sell your team to potential members in the introduction
    • skills describe your team's core compentancy
    • wants describe what you are looking for to fill out your team
    • strengths describe where your team shines the best
    • weaknesses list where your team is lacking or needs to improve
    • availability discusses the details of when or how your team is available to work on projects
    • fpr is short for Function Point Ratio which you should leave as zero unless you are into Function Point Analysis
    • the face book field is for integration with facebook
  • click the Add button
  • click the display link

Adding a Member to a Team

  • click the Members link
  • click the Add button
  • fill out the form
    • select the newly created team in the team drop down list
    • select a team member in the user drop down list
    • the code is used as a lookup value
    • select the role that this member will play on this team
      • an analyst will be tasked to write use-cases that cover each requirement once the release has been frozen
      • a software architect will be tasked to review each use-case that has been frozen
      • a developer will be tasked to review each design that has been frozen
      • a developer will be tasked to code each design once it has been approved
      • each quality assurance engineer will be tasked to write test plans for approved use-cases
      • JOAT means Jack of All Trades and will get all of the above tasks
  • click the Add button
  • rinse and repeat until all members have been established for this team
  • click the newly created project in the green Projects area along the right hand side of the page

Adding a Team to a Project

  • click the Teams link
  • click the Add button
  • fill out the form
    • the code is used as a lookup value
    • select the newly created team
    • select the appropriate role
    • more on teams, members, and roles
      • On a small project, you will most probably have one JOAT team with every member being a JOAT.
      • On a mediam project, consider having one JOAT team with every member serving a different role.
      • On a large project, the best practice recommentation is to have multiple teams where each team serves a different role. All the members of each team serve the same role as the team itself.
    • enter a description of the current status of the team on this project
    • click the Add button