Rules

Secret ingredients to quality software

Edit
Info

Do you use a Project Portal for your team and client?

Created on 05 Jun 2016 | Last updated by Jleerson on 26 Feb 2021 01:31 AM (about 2 months ago)

When a new developer joins a project, there is often a sea of information that they need to learn right away to be productive. This includes things like:

  1. Who the Product Owner is and who the Scrum Master is
  2. Where the backlog is
  3. Where the automated builds are
  4. Where the staging and production environments are
  5. How to set up the development environment for the project

Make it easy for the new developer by putting all this information in a central location like the Visual Studio dashboard.

plaindashboard

2016 06 06 8 00 55
Figure: Bad Example - Don't stick with the default dashboard, it's almost useless

2016 06 06 9 15 14
Figure: Good Example - This dashboard contains all the information a new team member would need to get started

The dashboard should contain:

  1. Who the Product Owner is and who the Scrum Master is
  2. The Definition of Ready and the Definition of Done
  3. When the daily standups occur and when the next sprint review is scheduled
  4. The current sprint backlog
  5. Show the current build status
  6. Show links to:

    • Staging environment
    • Production environment
    • Any other external service used by the project e.g. Octopus Deploy, Application Insights, RayGun, Elmah, Slack

Your solution should also contain the standard _Instructions.docx to your solution file for additional details on getting the project up and running in Visual Studio.

For particularly large and complex projects you can use an induction tool like SugarLearning to create a course for getting up to speed with the project.

2016 06 06 7 18 43

Adam CoganAdam Cogan
Eric PhanEric Phan

We open source. This page is on GitHub