Request Document for Micro-Project
Last updated on 2026-06-08 | Edit this page
Request Document for Micro-Project
The following sections follow the typical structure of the “RSE Request Document” at University of Manchester used as part of the departmental Project Demand and Monitoring Process. It is used to record initial discussions with the customer and outlines the broad scope and gist of the project. Where possible, it also suggests fundamental requirements to help define the potential solution enough such that project effort and duration may be estimated. This information is then used for funding applications and/or scheduling and resourcing.
In your teams, you may also receive an initial request from your academic customers in a similar form, depending on your organisation’s existing workflow, which will form the basis for the work you do for them.
For this training course, the Request Document below represents the scope of the development work to allow population of the backlog.
Project Background
A local community group want to create a Collaborative Multicultural Recipe Book to celebrate the diverse range of cuisines represented in their neighborhood. The project’s goal is to collect, organize, and present recipes from various cultural backgrounds, showcasing the traditions, flavors, and cooking techniques that make each cuisine unique.
The recipe book will be compiled from contributions by community members, resulting in a well-structured, high-quality collection that can be shared as both a professionally printed book and a downloadable digital PDF.
The collection will be organized by cuisine type (e.g., Italian, Indian, Mexican, Japanese) and will follow a consistent structure and style, ensuring that every recipe is easy to read, follow, and reproduce. Contributors will be asked to provide their recipes in Markdown format to ensure uniformity and ease of editing.
The project will focus exclusively on:
- Content gathering (recipes, introductions, and images)
- Organization and categorization (correct classification by cuisine)
- Editing and proofreading for accuracy and clarity
- Quality control to maintain consistent formatting and style
No software development or custom application building will be required; the end product will be the recipe collection itself, ready for printing and digital distribution.
Requirements
All recipes must be stored in the following folder structure to ensure easy organisation:
recipes/
│
├── italian/
│ └── spaghetti_carbonara.md
│
├── indian/
│ └── chicken_tikka.md
│
├── mexican/
│ └── tacos_al_pastor.md
│
└── japanese/
└── sushi_rolls.mdContent Guidelines for Each Recipe File
Each recipe file should contain:
- Recipe Title
- Cuisine
- Preparation Time
- Cooking Time
- Serving Size
- Ingredients (clear list with quantities)
- Method (step-by-step instructions)
- Serving Suggestions
- Photo (optional)
Primary Goals of the Project
Gather at least three recipes for each cuisine category.
- Ensure all recipes follow the agreed structure and are placed in the correct folder.
- Provide high-quality photographs for at least half of the recipes.
- Include a short cultural introduction for each cuisine section.
- Proofread and edit all recipes to ensure clarity.
The user stories for the first two epics will be provided in the repositories that are given to the groups. Once learners have got through the first sprint, please try your best to keep any of these further suggestions hidden from the learners during the workshop, and instead allow the learners to organically discover what you want them to do. If they get really stuck and ask you for the advice, then use the suggestions here as a guide.
Epic 1: Project Setup & Content Standards
User Story 1.1 – Recipe Markdown Template
As a contributor, I want a standard Markdown recipe template, so that all recipes are consistent and easy to edit and publish.
Acceptance Criteria
- Template includes all required sections (title, cuisine, times, ingredients, method, etc.)
- Uses consistent Markdown headings and lists
- Template is shared with all contributors
User Story 1.2 – Folder Structure & Naming Conventions
As a project editor, I want a defined folder and filename structure, so that recipes are easy to organise and locate by cuisine.
Acceptance Criteria - Cuisine folders match agreed names (e.g. italian, indian) - Filenames use lowercase and underscores - Examples are documented
User Story 1.3 – Contributor Guidelines
As a community contributor, I want clear submission guidelines, so that I know how to format and submit my recipe correctly.
Acceptance Criteria - Guidelines explain Markdown usage - Submission process is clearly described - Image requirements are documented
User Story 1.4 – Quality Standards Definition
As an editor, I want clear quality standards, so that I can consistently assess recipes and images.
Acceptance Criteria - Standards defined for formatting, clarity, and images - Standards are agreed by the project team - Standards are accessible to reviewers
Epic 2: Recipe Content Gathering
User Story 2.1 – Recruit Contributors
As a project organiser, I want to recruit community contributors, so that each cuisine has enough authentic recipes.
Acceptance Criteria - Contributors identified for each cuisine - Minimum target of three recipes per cuisine is feasible
User Story 2.2 – Italian Recipes
As an editor, I want at least three Italian recipes collected in Markdown, so that the Italian section is complete.
Acceptance Criteria - Minimum of three Italian recipes received - Recipes follow the standard template - Files are stored in recipes/italian/
User Story 2.3 – Indian Recipes
As an editor, I want at least three Indian recipes collected in Markdown, so that the Indian section is complete.
Acceptance Criteria - Minimum of three Indian recipes received - Recipes follow the standard template - Files are stored in recipes/indian/
Epic 3: Cultural Introductions
User Story 3.1 – Italian Cuisine Introduction
As a reader, I want a short Italian cuisine introduction, so that I understand the cultural context of the recipes.
Acceptance Criteria - Introduction is concise and informative - Content is culturally accurate - File is included in the Italian section
User Story 3.2 – Indian Cuisine Introduction
As a reader, I want a short Indian cuisine introduction, so that I understand the diversity and traditions behind the dishes.
Acceptance Criteria - Covers cultural and culinary background - Language is accessible and respectful
User Story 3.3 – Mexican Cuisine Introduction
As a reader, I want a short Mexican cuisine introduction, so that I understand key ingredients and traditions.
Acceptance Criteria - Introduction reflects cultural heritage - Fits the overall style of the book
Epic 4: Photography & Visual Assets
User Story 4.1 – Photo Standards
As an editor, I want clear photo requirements, so that submitted images are suitable for print and PDF.
Acceptance Criteria - Resolution and format specified - Naming and placement rules defined
Epic 5: Editing & Proofreading
User Story 5.1 – Technical Proofreading
As a reader, I want recipes to be clear and accurate, so that I can follow them without confusion.
Acceptance Criteria - Steps are logically ordered - Quantities and timings are clear
User Story 5.2 – Language & Style Editing
As an editor, I want consistent language and tone, so that the book reads as a single cohesive work.
Acceptance Criteria - Terminology is consistent - Tone matches agreed style guidelines
Epic 6: Final Quality Control & Publication Readiness
User Story 6.1 – Completeness Audit
As a project stakeholder, I want to confirm each cuisine section is complete, so that the book meets its stated goals.
Acceptance Criteria - ≥3 recipes per cuisine - Introduction present for each cuisine
User Story 6.2 – Cross-Collection Consistency Review
As an editor, I want consistency across the entire collection, so that the final book feels professional.
Acceptance Criteria - Consistent formatting across cuisines - No structural deviations