You can [customize your project overview page](%{base_url}/my_projects_overview/demo-project/page_layout) to add important information, such as project description, important links, work packages overview, news, and much more.
**Youcan:**
*edit the project overview by clicking on the gear icon,
*add a project description,
*add links to important project information or custom reports,
Please activate further [Modules](%{base_url}/projects/demo-project/settings/modules) in the Project settings in order to have more features in your project.
**Youcan:**
*add a Scrum module (Backlogs),
*add time tracking, reporting, and budgets (Time Tracking, Cost Reports, Budgets),
Please create work packages for your project. Go to [Work package](%{base_url}/projects/demo-project/work_packages) and click the green +Create button.
**Youcan**:
*create any type of work, e.g. features, tasks, bugs, risks, ideas,
*add a title and description,
*add attachments via copy and paste to the description,
*set status, priority and assign it to a team member,
*insert any custom field to the forms.
**Visuals**:
![create work package](##attachment:"create_work_package.jpg")
[Edit a work package](%{base_url}/projects/demo-project/work_packages/41/activity) by double clicking on a row in the list view or open the split screen with the "i".
**Youcan**:
*change title or description,
*assign it to a team member,
*comment on topics or notify team members with @-notifications,
*set status, priority, finish dates or other custom fields,
*include documents or screenshots with copy & paste,
*add relations to other work packages,
*change forms in the Administration settings.
**Visuals**:
![edit work package](##attachment:"edit_work_package.jpg")
In this wiki you can collaboratively create and edit pages and sub-pages to create a project wiki.
**Youcan:**
*insert text and format it with the toolbar,
*insert text and images with copy and paste,
*paste formatted text directly from MSOffice documents,
*create a page hierarchy by inserting parent pages,
*use makros to include, e.g. table of contents, work packages lists or Gantt charts,
*include wiki pages in other text fields, e.g. project overview or meetings,
*reference tickets with one, two or three "#"+ticket number, depending on what information should be displayed,
*include links to other documents,
*view the change history,
*view as Mardown.
**Moreinformation:**
https://www.openproject.org/help/wiki/
children:
- title:Project documentation
content:|
This is a sub-page of the wiki. You can change this by editing the Parent page (Click the _EDIT_ button and see bottom of the page).
## Project scope
## Deliverables
children:
- title:Project manual
content:''
scrum-project:
name:Scrum project
identifier:your-scrum-project
description:|
*Thisis a Scrum demo project.*
You can edit the project description in the [Project settings -> Description](%{base_url}/projects/your-scrum-project/settings).
timeline:
name:Timeline
modules:
- backlogs
- news
- wiki
- work_package_tracking
news:
- title:Welcome to your Scrum demo project
summary:>
We are glad you joined.
In this module you can communicate project news to your team members.
description:This is the news content.
versions:
- name:Bug Backlog
sharing:none
status:open
- name:Product Backlog
sharing:none
status:open
start:15
- name:Sprint 1
sharing:none
status:open
start:4
duration:7
wiki:
title:Sprint 1
content:|
### Sprint planning meeting
_Please document here topics to the Sprint planning meeting_
*Time boxed (8 h)
* Input:Product Backlog
* Output:Sprint Backlog
* Divided into two additional time boxes of 4 h:
*The Product Owner presents the team the [Product Backlog](%{base_url}/projects/your-scrum-project/backlogs) and the priorities and explanes the Sprint Goal, to which the team must agree. Together, they prioritize the topics from the Product Backlog which the team will take care of in the next sprint. The team committs to the discussed delivery.
*The team plans autonomously (without the Product Owner) in detail and breaks down the tasks from the discussed requirements to consolidate a [Sprint Backlog](%{base_url}/projects/your-scrum-project/backlogs).
### Daily Scrum meeting
_Please document here topics to the Daily Scrum meeting_
*Short, daily status meeting of the team.
*Time boxed (max. 15 min).
*Stand-up meeting to discuss the following topics from the [Task board](##sprint:"Sprint 1").
*What do I plan to do until the next Daily Scrum?
*What has blocked my work (Impediments)?
*Scrum Master moderates and notes down [Sprint Impediments](##sprint:"Sprint 1").
*Product Owner may participate may participate in order to stay informed.
### Sprint Review meeting
_Please document here topcis to the Sprint Review meeting_
*Time boxed (4 h).
*A maximum of one hour of preparation time per person.
*The team shows the product owner and other interested persons what has been achieved in this sprint.
* Important:nodummies and no PowerPoint! Just finished product functionality (Increments) should be demonstrated.
*Feedback from Product Owner, stakeholders and others is desired and will be included in further work.
*Based on the demonstrated functionalities, the Product Owner decides to go live with this increment or to develop it further. This possibility allows an early ROI.
### Sprint Retrospective
_Please document here topcis to the Sprint Retrospective meeting_
*Time boxed (3 h).
*After Sprint Review, will be moderated by Scrum Master.
* The team discusses the sprint:what went well, what needs to be improved to be more productive for the next sprint or even have more fun.
- name:Sprint 2
sharing:none
status:open
types:
- :default_type_task
- :default_type_milestone
- :default_type_phase
- :default_type_epic
- :default_type_user_story
- :default_type_bug
categories:
- Category 1 (to be changed in Project settings)
queries:
- name:Project plan
status:open
sort_by:id
type:
- :default_type_milestone
- :default_type_phase
timeline:true
- name:Product backlog
status:open
version:Product Backlog
group_by:status
sort_by:status
columns:
- id
- type
- subject
- priority
- status
- assigned_to
- story_points
- name:Sprint 1
status:open
version:Sprint 1
hierarchy:true
columns:
- id
- type
- subject
- priority
- status
- assigned_to
- done_ratio
- story_points
- name:Tasks
status:open
type::default_type_task
hierarchy:true
work_packages:
- subject:New login screen
status::default_status_in_specification
type::default_type_user_story
version:Product Backlog
position:3
- subject:Password reset does not send email
status::default_status_confirmed
type::default_type_bug
version:Bug Backlog
position:1
- subject:New website
status::default_status_new
type::default_type_epic
start:26
duration:0
children:
- subject:Newsletter registration form
status::default_status_new
type::default_type_user_story
version:Product Backlog
position:6
- subject:Implement product tour
status::default_status_new
type::default_type_user_story
version:Product Backlog
position:4
- subject:New landing page
status::default_status_specified
type::default_type_user_story
version:Sprint 1
position:2
story_points:3
start:26
duration:0
children:
- subject:Create wireframes for new landing page
status::default_status_in_progress
type::default_type_task
version:Sprint 1
start:26
duration:0
- subject:Contact form
status::default_status_specified
type::default_type_user_story
version:Sprint 1
position:5
start:21
duration:0
story_points:1
- subject:Feature carousel
status::default_status_specified
type::default_type_user_story
version:Sprint 1
position:3
story_points:5
children:
- subject:Make screenshots for feature tour
status::default_status_closed
type::default_type_task
version:Sprint 1
- subject:Wrong hover color
status::default_status_confirmed
type::default_type_bug
version:Sprint 1
position:4
story_points:1
start:21
duration:0
- subject:SSL certificate
status::default_status_specified
type::default_type_user_story
version:Product Backlog
position:1
start:22
duration:1
- subject:Set-up Staging environment
status::default_status_in_specification
type::default_type_user_story
version:Product Backlog
position:2
start:23
duration:0
- subject:Choose a content management system
status::default_status_specified
type::default_type_user_story
version:Product Backlog
position:7
start:24
duration:1
- subject:Website navigation structure
status::default_status_specified
type::default_type_user_story
version:Sprint 1
position:7
story_points:3
start:25
duration:0
children:
- subject:Set up navigation concept for website.
status::default_status_new
type::default_type_task
version:Sprint 1
start:25
duration:0
- subject:Internal link structure
status::default_status_new
type::default_type_user_story
version:Product Backlog
position:5
start:25
duration:0
- subject:Develop v1.0
status::default_status_new
type::default_type_phase
start:14
duration:3
- subject:Release v1.0
status::default_status_new
type::default_type_milestone
start:18
duration:0
relations:
- to:Develop v1.0
type:follows
- subject:Develop v1.1
status::default_status_new
type::default_type_phase
start:21
duration:3
- subject:Release v1.1
status::default_status_new
type::default_type_milestone
start:25
duration:0
relations:
- to:Develop v1.1
type:follows
- subject:Develop v2.0
status::default_status_new
type::default_type_phase
start:28
duration:3
- subject:Release v2.0
status::default_status_new
type::default_type_milestone
start:32
duration:0
relations:
- to:Develop v2.0
type:follows
wiki:|
### Sprint planning meeting
_Please document here topics to the Sprint planning meeting_
*Time boxed (8 h)
* Input:Product Backlog
* Output:Sprint Backlog
* Divided into two additional time boxes of 4 h:
*The Product Owner presents the team the [Product Backlog](%{base_url}/projects/your-scrum-project/backlogs) and the priorities and explanes the Sprint Goal, to which the team must agree. Together, they prioritize the topics from the Product Backlog which the team will take care of in the next sprint. The team committs to the discussed delivery.
*The team plans autonomously (without the Product Owner) in detail and breaks down the tasks from the discussed requirements to consolidate a [Sprint Backlog](%{base_url}/projects/your-scrum-project/backlogs).
### Daily Scrum meeting
_Please document here topics to the Daily Scrum meeting_
*Short, daily status meeting of the team.
*Time boxed (max. 15 min).
*Stand-up meeting to discuss the following topics from the Task board.
*What do I plan to do until the next Daily Scrum?
*What has blocked my work (Impediments)?
*Scrum Master moderates and notes down Sprint Impediments.
*Product Owner may participate may participate in order to stay informed.
### Sprint Review meeting
_Please document here topcis to the Sprint Review meeting_
*Time boxed (4 h).
*A maximum of one hour of preparation time per person.
*The team shows the product owner and other interested persons what has been achieved in this sprint.
* Important:nodummies and no PowerPoint! Just finished product functionality (Increments) should be demonstrated.
*Feedback from Product Owner, stakeholders and others is desired and will be included in further work.
*Based on the demonstrated functionalities, the Product Owner decides to go live with this increment or to develop it further. This possibility allows an early ROI.
### Sprint Retrospective
_Please document here topcis to the Sprint Retrospective meeting_
*Time boxed (3 h).
*After Sprint Review, will be moderated by Scrum Master.
* The team discusses the sprint:what went well, what needs to be improved to be more productive for the next sprint or even have more fun.
