This article has two topics: the first is to demonstrate the STAR (Situation-Task-Action-Result) framework, and the second is to tell about my experience of introducing the board into the technology development cycle that allows you to perform geophysical exploration. The article will be useful for novice group leaders and those who are faced with problems in prioritizing tasks.
STAR
STAR is an acronym for Situation, Task, Action, Result. It is great for answering during technical interviews, keeping you focused. For example, the question may be about an example of a situation in which you did not have time to complete a task in a short time, or about some of your initiative. In fact, this is the answer plan:
I learned about STAR from this article , but do not limit the scope of application only to technical interviews. For example, I used STAR for the infographic when I gave a presentation on the implementation of acceptance testing. Power point template link here .
And in this article, STAR will help me to reveal the second topic, and at the same time it will be an example of use.
Situation
. R&D . , .
. , : (embedded developers). : . . , . .
Task
. - .
Action
1. c (Backlog, ToDo, In Progress, Pending, Done).
2. backlog, . : (1, 2, 4, 8, 20, 40, 100). . .
3. odoo (erm-), , . Trello. , . :
4. , . . , . . ToDo 5 * 8 * 3.5 = 140 . , . , , ..
5. , R&D, . , legacy, ToDo.
6. - . bus factor . , , .
7. , , . , .
8. . , , - . backlog, , , .
Result
.
: , .
. , , , . , - .
We didn't have any fires.
Communication between teams and project managers was environmentally friendly.
For the honesty of the article, I must note that we did not have time to complete our projects in the initial deadline, but we achieved transparency.
We no longer use the Gantt chart in our development cycle planning.
At the end, I would like to say thank you to the book Scrum (Jeff Sutherland) , thanks to which the steps were born to solve our problem.