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 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.
_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.
