-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
6cb920c
commit 554579a
Showing
17 changed files
with
75 additions
and
77 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters