scrum personal time manager ihr scrum master

The basic idea of a Scrum Story - write down all you have to do and do it!

Optimize your time management skills and team efficiency using Post-it notes and splitting your job into smaller pieces. 

Scrum Story
Scrum Story is a project or subproject which a Team has planned to do. It can be, for example,  a feature, desired by a customer, or a problem, which needs to be solved. 
Stories have a name, a serial number, they are usually distinguished by priority and they also have to be provided with test which proves if the Story is really done. A good Scrum Story should also be written by perspective of customer or the Project Owner

Summarizing, a Scrum Story points out easily and visible for everyone, who is involved, what your Team has to do, and what problems need to be solved. 

Scrum Story includes a few components: 
Scrum Story Test
For each Story you have to write a Test. Basically Tests help you to understand what is the Team’s goal in every Story. 
The Scrum Story Tasks are transparent for customers and the Team, so everyone knows what the goal is. 
A Test also  examine if the Scrum Story is done as it is supposed to be.

Scrum Tasks
After the Scrum Stories have been scrumed and prioritized, and everyone knows what the Test is, the Team has to write down the single Scrum Tasks. 
Tasks are required for a Scrum Story and they are determined by the Team during Sprint Planning. Tasks have a specific name (what needs to be done) and are marked with Scrum Points (how much time/efford is needed for the task). It is important that the Scrum Tasks aren’t too big, they should last between 2 and 4 hours of work, maximum 2 days. If a Tasks is bigger than 2 days, it’s too big and you have to split it into smaller Tasks. 

Some advantages of splitting Stories into Tasks:

- you know every step you should do to get closer to the finish line, 
- you also know how long each tasks will take, so 
- you can predict feasibility of the Sprint. 

There might be situations when all the to-do-tasks don’t seem fit in one Sprint - in this situation  your team has to talk to the Project Owner to find out which Tasks can move to the next Sprint. 
If it looks like the Team could do more than expected, then it’s allowed to add more Tasks during the Sprint.

Scrum Points
The Scrum Points are basically an abstract value for the Scrum Team’s capabilities in a specific time, so they show how much time each Task will take to be done. 
Scrum Points are used in calculating the Velocity of the team members. The team discusses the number of Scrum Points for each single Task and Story by playing Planning Poker.

Planning Poker is an estimation technique. Team members use this game to decide how much work (Scrum Points) every task will take by their own, and compare the results with those of the other team member. Different opinions of how much effort every task or story needs to be done, have to be discussed until your team reaches consensus. Discussions helps your team understanding each Task’s complexity.

You will obtain more accurate empirical values from Sprint to Sprint by tracking the “done” Scrum Points. 
So you can calculate your realistic workload with Scrum Point calculation.