Our team knows what they have to do. In most cases I say this because, of course, there can always be new situations where it is good to have a more experienced person like me give my point of view. That helps a lot to find a solution sooner.
Although in theory it is not necessary to give many explanations about some repetitive tasks, it is necessary to do so. Let me tell you.
Planning the task
This is what comes first. Sometimes it is necessary thailand whatsapp number data for two people to do it, other times it is enough for one person to do it. For simple things, 5-10 minutes of dedication, for others, more like 30-60 minutes or even several sessions. The important thing is this:
- Don’t mix topics and focus on that task only.
- Break down the task into simple, actionable steps.
- Plan when they are going to be carried out.
- Estimate the effort that the task will require.
- Give it a priority so that later decisions can be made about the order in which tasks will be executed.
- Assign responsibilities to that task (responsible person, the one who executes, the one who is informed).
Communicate with the rest of the team
Task communication can manifest itself in different ways:
- Organize a meeting to coordinate a suitable platform not only makes different steps of the task between different team members.
- Document the task in Jira and fill in all the fields (sprint, epic, description, story points, responsible).
- Following up. Also checking that a task is being done and is being done is part of communication. In this part we still fail a lot.
Execute a task
It’s time to take action. What do you need to consider?
- Complete the task at the planned time. That’s what we organize sprints for.
- Communicate about the status of a task in case it is malaysia data delayed or has many story points so it cannot be finished in one session (Jira task comments).
- Keep the rest of the team informed at all times about important and relevant tasks for the team (especially those related to a more immediate impact on sales and costs).
- Thinking about the next step now.
Engineers may also see something in the Deming PDCA cycle ( Plan-Do-Check-Act ). In reality, it is nothing more than that. What we often lack is thinking about the next action once the previous one is finished.
I give you an example of a task chain
- Place order for new product from supplier in China.
- Documentation in our investor tool.
- Plan design and text creation tasks.
- Think about packaging for shipping to Amazon warehouses.
- Upload to the web and other marketplaces.