today I want to make a short recording of the following video: Introduction to Jira & Agile and Project management.
Actually I just want to have short text version of Dan Chuparkoff's advices.
- Task is something that is bigger then 30 minutes but smaller then 3 days to complete. It is practical don't have tasks that take more then one day to do.
- You can't wait in the middle of the task. If you are waiting in the middle of the task, then take another look, maybe you have series of tasks.
- You can be in three modes: in progress, done, not started.
- Estimating is hard, but use estimates. And use story points, not the hours.
- There are different kinds of story points.
- If you want other team members to see some additional fields during issue creation, you can configure them.
- Scrum and Canban are subsets of Agile
- Scrum is more concentrated on date of release
- Batches of work in scrum are named sprints.
- Kanban is concentrated on what is delivered without strict deadline in mind. It means that in Kanban there is not plan, no sprints.
- Jira has Plan mode for scrum sprints
- You can tag your tasks with some labels. For example tag books you need to read.
- You drag staff from Backlog to next sprint.
- As usually sprints length is two weeks. One week sprint is to small. You start and stop to often.
- For dependencies you can link tasks together
- Create Epics first
- To start spring, click at button start spring
- You can extend workflow with additional steps ( one of the customers of Dan has 8000 stages in workflow)
- You can create quick filter in order to see tasks for what you need.
- For sprint you can pull tasks from differnt Epics
- In each sprint try to move a bit all of your epics
- Burndown is idea that a lot of people try to look for results.
- Burndown has two lines: red is how your team actually going, and other shows how it should work in ideal
- You can make differnet kinds of search, even with JQL ( Jira Query Language )
Some explanations about some points which are not straight forward.
For point 1. If your task will be not bigger then 1 day then you'll have opportunity to shuffle your tasks every single day. But if your tasks are bigger, say 2 or 3 days that you'll be able to shuffle your tasks every 2 or 3 days.
For point 4 and 5 Dan makes some kind of story point cheating:
30 minutes = 1 story point
1 hour = 2 story point
2 hours = 4 story points
4 hours = 8 story points
1 day = 16 story points
2 days = 32 story points
3 days = 48 story points
The more you practice in making estimates the better you'll become in making realistical estimates.
Make sure that your team has the same estimates between each member in order to have the same measurement approach.
For points 22 and 23 following additions. Don't add to much tasks to your sprint. Otherwise your burndown chart will not look nice. Second advice is make a big tv, visible to everybody in your team. That will help your team to see how they are doing and encourage them to close their tasks not prior to the end of the sprint but sooner.