added planning activities in line with team charter

src/content/docs/activities/planning.mdx

@@ -215,12 +215,13 @@ Provide a risk management plan detailing risks, their categorization (impact/lik
 
 <Badge text="Individual Activity" variant="success" class="mb-6"/>
 
-Set up a Kanban board to visualize and manage your project’s workflow effectively.
+Set up a Kanban board to visualize and manage your project's workflow effectively.
 
 1. Create Columns: Set up key stages like “To Do,” “In Progress,” and “Done” (or project-specific stages).
 2. List Tasks: Break down the project into individual tasks or user stories and add them to the “To Do” column.
 3. Manage Workflow: Move tasks across columns as work progresses to visualize progress.
 4. Limit Work in Progress (WIP): Set WIP limits to avoid overloading team members.
+5. Team Agreement: Discuss the process and tool with your team and ensure everyone agrees.
 
 Provide a screenshot of your Kanban board and a brief explanation of its structure.
 
@@ -235,4 +236,43 @@ Identify and categorize project stakeholders to ensure effective communication a
 - Define Communication Strategies: Establish how and when to communicate with each stakeholder category (e.g., regular updates, feedback sessions).
 - Review and Update: Regularly reassess the stakeholder map as the project evolves.
 
-Provide a stakeholder map and a plan outlining communication strategies for each group.
+Provide a stakeholder map and a plan outlining communication strategies for each group.
+
+## Definition of Done
+
+<Badge text="Individual Activity" variant="success" class="mb-6"/>
+
+The [Definition of Done (DoD)](https://www.atlassian.com/agile/project-management/definition-of-done) establishes clear criteria for when tasks, features, or the overall project can be considered complete.
+
+1. List Completion Criteria: Define specific conditions that must be met for each task or feature to be marked as “done” (e.g., all tests passed, documentation updated, code reviewed).
+2. Include Quality Standards: Ensure the criteria cover quality aspects like performance benchmarks, usability, or security.
+3. Team Agreement: Discuss the definition with your team and ensure everyone agrees.
+
+Provide a document outlining the agreed-upon Definition of Done for your project.
+
+## Software Release and Versioning
+
+<Badge text="Individual Activity" variant="success" class="mb-6"/>
+
+Plan the release process for your software, including version control and deployment strategies.
+
+1. Define [Release Process](https://www.manageengine.com/products/service-desk/it-release-management/what-is-release-management.html): Outline steps for preparing the software for release (e.g., final testing, documentation updates, packaging).
+2. Establish [Versioning Scheme](https://en.wikipedia.org/wiki/Software_versioning): Choose a versioning system (e.g., Semantic Versioning) to track software updates (e.g., 1.0.0 for major releases, 1.0.1 for patches).
+3. Plan Deployment: Identify how and where the software will be deployed or accessed (e.g., cloud platform, local servers, GitHub repository assets).
+4. Team Agreement: Discuss the process with your team and ensure everyone agrees.
+
+Submit a release plan document that includes versioning details and deployment steps.
+
+##  Software Development Process
+
+<Badge text="Individual Activity" variant="success" class="mb-6"/>
+
+Define and plan the software development process for your project to ensure clear workflow and task management.
+
+1. Choose a Development Methodology: Select an approach (e.g., [Agile](https://www.atlassian.com/agile), [Waterfall](https://www.atlassian.com/agile/project-management/waterfall-methodology), [SCRUM](https://www.atlassian.com/agile/scrum)) that fits your project.
+2. Outline Development Phases: Break down the process into phases such as planning, design, implementation, testing, and deployment.
+3. Set Milestones: Establish key milestones and goals for each phase.
+4. Assign Roles: Clarify team roles and responsibilities at each stage.
+5. Team Agreement: Discuss the process with your team and ensure everyone agrees.
+
+Provide a document outlining the chosen process, phases, milestones, and team roles.

src/content/docs/activities/reflective.mdx

@@ -46,6 +46,7 @@ Find an [ACM Tech Talk](https://learning.acm.org/techtalks-archive) of some rele
 
 ## Watch a Documentary
 
+<Badge text="Individual Activity" variant="success" class="mb-6"/>
 <Badge text="Team Activity" variant="note" class="mb-6" />
 
 Watch a documentary film related to your project. Each team member writes a paragraph about a different aspect of the film that is relevant to the project.

src/content/docs/activities/requirements.mdx

@@ -51,13 +51,17 @@ For each hypothesis:
 3. Provide a clear and professional summary of the results of the test (insights, etc.)
 4. If your initial hypothesis is false, provide a pivot hypothesis.
 
+If working on this activity as a team, have each different person focus on a different set of hypotheses.
+
 ## 🔥 User Story Mapping (Use Cases and Scenarios)
 
 <Badge text="Individual Activity" variant="success" class="mb-6"/>
 <Badge text="Team Activity" variant="note" class="mb-6" />
 
 After reading this [User Story Mapping](https://www.nngroup.com/articles/user-story-mapping/) article from the Nielsen Norman Group, create a comprehensive user story map for your project, and include an initial written set of epics and user stories.
 
+If working on this activity as a team, have each different person focus on a different set of stories.
+
 ## User's Emotional Objectives
 
 <Badge text="Individual Activity" variant="success" class="mb-6"/>
@@ -98,6 +102,8 @@ Develop a preliminary user manual that outlines how end-users will interact with
 
 Submit a draft of the user manual with clear instructions on using the main features of your system.
 
+If working on this activity as a team, have each different person focus on a different subset of the manual.
+
 ## Define Your Research Questions
 
 <Badge text="Individual Activity" variant="success" class="mb-6"/>