Getting started with Jira and Confluence for a team of 10

I have already talked about this . We will soon start to function as a “normal” company. Although… it is not entirely true, honestly. If we only achieve 80% of what I have in mind, we will function much better than a normal company.

Kick-off meeting with the entire team

We are carrying out the work with the help thailand whatsapp number data of an external person. Although I have not worked differently in the last three years on client projects, I have wanted to have the support of someone outside the company, to detect improvements that can only be made by being neutral and free of prejudices or emotions.

At the meeting we did the following:

  • We have explained what Jira and Confluence are and how they work.
  • We’ve reviewed the structure we’ve put in place for Jira and Confluence.
  • We have introduced the concept of sprints and how we are going to start working with them.
  • Q&A with the team.

WhatsApp Data

Follow-up meeting to plan the first sprint

Yesterday we had the kick-off meeting and today our clients have help us out several times we have the first meeting to plan the first sprint that will start next week. This is what we are going to do.

  1. Analyze the task backlog already created.
  2. Add tasks to the backlog with those tasks that are missing.
  3. “Throw” tasks from the backlog into the sprint.

As story points we are going to use numbers from the Fibonacci sequence: 1, 2, 3, 5, 8, 13, 21, 34, etc.

This is how to use them when awarding points to tasks:

  • 1 : Simple task. In our case it would be something like “Create a title for a listing” when we already have all the information at hand.
  • 2. Simple task. It could be the same example as above but in this case we have to do a brief keyword analysis.
  • 3. Simple task but requires a little more work. Continuing with the example above, you would create the full description for this listing.
  • 5. A slightly more demanding task. We have database d most things clear but several steps are required and there is some uncertainty. You could try to resolve an issue with Amazon support.
  • 8. Elaborate and demanding task. We are facing a new incident at Amazon that we have not had before. There are parts that we control but a large part we do not.
Scroll to Top