Beginnings are always good. The same is happening with Jira and Confluence. We are transitioning from Asana to Jira and starting with Confluence. This part is easy. The difficult part is to make it work in the long term, achieving the results we are looking for, which is greater productivity in our tasks.
Start documentation in Confluence
This is still going to take some sweden whatsapp number data getting used to. Especially in the early days, it is being used more as a file storage site. That is not the idea. We want to have a “Wikipedia for business.” To do this, it is a matter of creating pages. Here is what will happen:
- We’ll be creating pages like crazy.
- We need to regroup those pages into sections.
- We group, delete and join different pages.
It’s a learning process. We’ll get there.
Estimate the tasks
I think I mentioned it already. We are using tyumen from a small northern villae Fibonacci numbers: 1, 2, 3, 5, 8, 13, 21, 34, etc. According to Scrum, time is not estimated. This is always a challenge for everyone. Let’s start and apply this sequence to represent increasing complexity and uncertainty at the task level. It will be crucial to know what capacity we have to complete tasks in each sprint.
Project structure in Jira
My initial idea was to have all the tasks from database d all the projects in a backlog but this does not work in Jira. To do this everything would have to be within the same project which at a structural level does not make much sense. This is something that I will have a meeting with today to see how to set it up in an optimal way for us.
We will create the listing from scratch to avoid the burden of negative reviews. I think we can have 30 sales per day for this product by Christmas. As I said, this is a learning experience. We have started the Scrum journey. Let’s see where it takes us.