This project is read-only.



Purpose and Scope

This document defines the project vision and requirements for Scrumptious. Since two main areas are covered in this document, it is logically broken into two sections. First, it establishes the business need for Scrumptious and outlines the high level requirements as needed to satisfy the specified business need. Then, it provides a more detailed look into those high-level requirements and lists constraints applicable to the development process.

This document should be read and understood by all system stakeholders with an interest in the detailed workings of the system. Most importantly, this includes those who are building the system and those who will use it to carry out their business responsibilities.


Business Opportunity


Microsoft Team Foundation Server (TFS) is a configuration management (CM) solution which encompasses work item tracking, version control, build automation, centralized collaboration, and reporting. To ensure a high degree of customization for each team project, TFS supports process templates, which form the basis for how team members will interact with TFS. The default process templates delivered with TFS (as of v1) are MSF Agile and MSF CMMI. The majority of projects seem to use MSF Agile and customize it to meet their needs. Over time, as the scrum methodology has become more prevalent, more and more teams have set forth to augment their process template with scrum concepts. Of course, third party process templates were soon out; however, they all focused solely on managing a scrum effort as opposed to managing a software project which coincidentally uses the scrum methodology. Based on this, the goal of Scrumptious is to provide tools to enhance the user experience for all project team members, specifically focused on proven practices around project, requirements, and work management.


Scrumptious is intended to start with the MSF Agile process template and augment it with scrum concepts. Over time, this will grow beyond scrum to provide other enhancements to ensure a higher level of productivity. The project is intended to be community-driven and will need to remain flexible for future releases.

System Context

Scrumptious will consist of a single process template focused on managing a team using the scrum methodology. As features are implemented and additional needs arise, the project's scope will most likely grow.

Stakeholder Summary


User Summary


Key Stakeholder and User Needs

Name Priority Concerns Current Solution Proposed Solution
Work Item Tracking High Separation of responsibility; traceability
Version Control Low None N/A N/A
Build Automation Low None N/A N/A
Centralized Collaboration Medium None N/A N/A
Reporting High Structured insight; quality oversight

Impact of Missed Opportunity

Should Scrumptious not be implemented according to specification, the only publicly-available method for efficiently managing a scrum within TFS will require sacrificing requirements and work management principles for scheduling.

Alternatives and Competition

We know and respect the fact that Scrumptious is not for everyone. The following are known scrum-based solutions built on TFS.
Tool Pros Cons
Scrum for Team System TBD TBD
Tackle TBD No TFS integration
VSTS Scrum Process Template TBD TBD

Proposed Solution

Proposed Feature-Sets

Work Item Tracking

  • Structured separation of project, requirements, and work management

Version Control

No changes planned at this time

Build Automation

No changes planned at this time

Centralized Collaboration

No changes planned at this time


No changes planned at this time

Future Considerations


Priority Systemic Qualities

In this section, we identify the primary quality of service requirements for Scrumptious. This list is not exhaustive but is intended to capture the most important requirements from a business perspective.

Environmental and Operational Constraints

Development Process and Team Constraints


Environmental and Technology Constraints


Delivery and Deployment Constraints


Service Level Requirements

The vast majority of the service-level requirements are handled by the parent system, TFS. The items listed below are specific to what is implemented by Scrumptious.

Users and Human Factors

End User Training

End user training shall be self-accomplished through available online help files and/or documentation.

Last edited Apr 20, 2007 at 5:04 AM by flanakin, version 2


No comments yet.