Skip to content

Commit

Permalink
Refactored template skeleton
Browse files Browse the repository at this point in the history
  • Loading branch information
benfortuna committed Dec 17, 2023
1 parent 6cb920c commit 554579a
Show file tree
Hide file tree
Showing 17 changed files with 75 additions and 77 deletions.
3 changes: 3 additions & 0 deletions docs/template/agile/backlog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
# iCal4j Template - Agile: Backlog

A Backlog represents a group of work items that may be associated with zero or more Sprints.
4 changes: 4 additions & 0 deletions docs/template/agile/criteria.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
# iCal4j Template - Agile: Criteria

A Criteria represents a set of customer requirements that are used to guide the defined work items. Also known
as Acceptance Criteria, Criteria document solution details for work items such as Epics and Stories.
4 changes: 4 additions & 0 deletions docs/template/agile/epic.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
# iCal4j Template - Agile: Epic

An Epic is used to group work items that combine to provide a larger feature. These features are typically
demonstrable in ceremonies such as showcases.
31 changes: 0 additions & 31 deletions docs/template/agile/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,34 +7,3 @@ Templates for working with Agile methodologies.
[Agile](https://agilemanifesto.org/principles.html) is a software development methodology that prioritises
collaboration between developers and users and responding rapidly to changing requirements. Agile
is also successfully applied more generally as a project management methodology.

## Sprint

A key aspect of many Agile implementations is to work in timeboxed iterations, often called sprints. Here we
provide a Sprint template to represent a single iteration that has an associated backlog of work items planned for the
iteration.

## Backlog

A Backlog represents a group of work items that may be associated with zero or more Sprints.

## Story

A Story represents a single work item that can be implemented and tested independently of others. Typically, each
Story will have its own acceptance criteria to define the parameters and constraints a working implementation.

## Epic

An Epic is used to group work items that combine to provide a larger feature. These features are typically
demonstrable in ceremonies such as showcases.

## Criteria

A Criteria represents a set of customer requirements that are used to guide the defined work items. Also known
as a Acceptance Criteria, Criteria document solution details for work items such as Epics and Stories.

## Retrospective

A Retrospective is a special kind of [Meeting](groupware.md#meeting) [Agenda](groupware.md#agenda) that aims to
reflect on current progress and practices to identify what works and what doesn't. As with a regular Agenda, any
points not discussed may be carried over to the next Retrospective Meeting.
7 changes: 7 additions & 0 deletions docs/template/agile/retrospective.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# iCal4j Template - Agile: Retrospective

A Backlog represents a group of work items that may be associated with zero or more Sprints.

A Retrospective is a special kind of [Meeting](groupware.md#meeting) [Agenda](groupware.md#agenda) that aims to
reflect on current progress and practices to identify what works and what doesn't. As with a regular Agenda, any
points not discussed may be carried over to the next Retrospective Meeting.
5 changes: 5 additions & 0 deletions docs/template/agile/sprint.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
# iCal4j Template - Agile: Sprint

A key aspect of many Agile implementations is to work in timeboxed iterations, often called sprints. Here we
provide a Sprint template to represent a single iteration that has an associated backlog of work items planned for the
iteration.
4 changes: 4 additions & 0 deletions docs/template/agile/story.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
# iCal4j Template - Agile: Story

A Story represents a single work item that can be implemented and tested independently of others. Typically, each
Story will have its own acceptance criteria to define the parameters and constraints a working implementation.
4 changes: 4 additions & 0 deletions docs/template/project/decision.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
# iCal4j Template - Project Management: Decision

A Decision captures agreement on a critical Project element that may be referred to or superseded at a later date.
Decisions are Project assumptions that ensure collaborators all agree on Project outcomes and deliverables.
47 changes: 1 addition & 46 deletions docs/template/project/index.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# iCal4j Template - Project
# iCal4j Template - Project Management

Project management templates.

Expand All @@ -7,48 +7,3 @@ Project management templates.
Project management focuses on the collaboration between individuals and teams to achieve specific outcomes. A project
may represent a time-bounded or unbounded collaboration, and is the focal point for tracking objectives, risk,
issues, etc. associated with the collaborative activities.

## Team

A Team is a group of individual members, working together to achieve common collaborative outcomes. Teams may be
hierarchical in that a Team can be a member of another Team.

## Project

A Project is represented as collaborative activity associated with one or more teams and/or individuals. Each Project
may have associated objectives, risks, issues, etc. that are used to guide collaborative activities.

## Objective

An Objective identifies a specific goal of a project, and may be used to group specific risks, issues and milestones.
Objectives should be high-level, and focus on the WHY aspects of a Project (i.e. what is the purpose of the project).

## Milestone

A Milestone represents a target within a project that may be associated with a specific Objective. The Milestone
defines the WHAT aspect of Project activities and are an opportunity to track progress within a Project.

## Task

A Task captures a specific activity undertaken by a team or individual. Each Task may be associated with a Milestone
such that progress towards Milestone completion may be accurately tracked.

## Risk

A Risk is used to track potential problems or issues associated with a Project. Essentially a Risk is an unrealised
issue, which has an associated likelihood and impact to a Project.

## Issue

Issues are challenges and blockers to Project Tasks. Resolution of an Issue may require additional Tasks to be
completed first.

## Decision

A Decision captures agreement on a critical Project element that may be referred to or superseded at a later date.
Decisions are Project assumptions that ensure collaborators all agree on Project outcomes and deliverables.

## Timesheet

A Timesheet is used to capture metrics related to Project effort. On a given day, week or month it may be useful
to track how much time is spent on specific Tasks for purposed such as financial reporting.
4 changes: 4 additions & 0 deletions docs/template/project/issue.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
# iCal4j Template - Project Management: Issue

Issues are challenges and blockers to Project Tasks. Resolution of an Issue may require additional Tasks to be
completed first.
4 changes: 4 additions & 0 deletions docs/template/project/milestone.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
# iCal4j Template - Project Management: Milestone

A Milestone represents a target within a project that may be associated with a specific Objective. The Milestone
defines the WHAT aspect of Project activities and are an opportunity to track progress within a Project.
4 changes: 4 additions & 0 deletions docs/template/project/objective.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
# iCal4j Template - Project Management: Objective

An Objective identifies a specific goal of a project, and may be used to group specific risks, issues and milestones.
Objectives should be high-level, and focus on the WHY aspects of a Project (i.e. what is the purpose of the project).
4 changes: 4 additions & 0 deletions docs/template/project/project.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
# iCal4j Template - Project Management: Project

A Project is represented as collaborative activity associated with one or more teams and/or individuals. Each Project
may have associated objectives, risks, issues, etc. that are used to guide collaborative activities.
4 changes: 4 additions & 0 deletions docs/template/project/risk.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
# iCal4j Template - Project Management: Risk

A Risk is used to track potential problems or issues associated with a Project. Essentially a Risk is an unrealised
issue, which has an associated likelihood and impact to a Project.
4 changes: 4 additions & 0 deletions docs/template/project/task.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
# iCal4j Template - Project Management: Task

A Task captures a specific activity undertaken by a team or individual. Each Task may be associated with a Milestone
such that progress towards Milestone completion may be accurately tracked.
4 changes: 4 additions & 0 deletions docs/template/project/timesheet.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
# iCal4j Template - Project Management: Timesheet

A Timesheet is used to capture metrics related to Project effort. On a given day, week or month it may be useful
to track how much time is spent on specific Tasks for purposed such as financial reporting.
15 changes: 15 additions & 0 deletions mkdocs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -86,8 +86,23 @@ nav:
- Appointment: template/groupware/appointment.md
- Project:
- Overview: template/project/index.md
- Project: template/project/project.md
- Objective: template/project/objective.md
- Milestone: template/project/milestone.md
- Task: template/project/task.md
- Risk: template/project/risk.md
- Issue: template/project/issue.md
- Decision: template/project/dedcision.md
- Decision: template/project/decision.md
- Timesheet: template/project/timesheet.md
- Agile:
- Overview: template/agile/index.md
- Sprint: template/agile/sprint.md
- Backlog: template/agile/backlog.md
- Story: template/agile/story.md
- Epic: template/agile/epic.md
- Criteria: template/agile/criteria.md
- Retrospective: template/agile/retrospective.md
- Workflow:
- Overview: template/workflow/index.md
- Catalog:
Expand Down

0 comments on commit 554579a

Please sign in to comment.