Do you use a Project Portal for your team and client?
8/06/2017 4:53 AM by
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:
- What the "Definition of Ready" and "Definition of Done" are
- Where the backlog is
- Where the automated builds are
- Where the staging and production environments are
- 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.
- Figure: Bad Example - Don't stick with the default dashboard, it's almost useless
- Figure: Good Example - This dashboard contains all the information a new team member would need to get started
The dashboard should contain:
The "Definition of Ready" and the "Definition of Done"
When the daily standups occur and when the next sprint review is scheduled
Who the product owner is and who the scrum master is
The current sprint backlog
Show the current build status
Show links to:
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
Sugar Learning to create a course for getting up to speed with the project.
Do you feel this rule needs an update?