TK and game development: transformation of a business task into a technical one The technical task for the developer should be sufficiently clear, unambiguous and comprehensive so that he can start work without unnecessary questions and clarifications. Without a clear TOR, team members will waste a lot of time on unnecessary communication. Therefore, it is better to consider the task, write it down in detail and record the general vision in the document. At OBRIO, even for a small task, we practice starting cards. We do not write down the smallest tasks in detail. When everyone is in context and understands what is being talke about, sometimes it is faster to complete this task than to describe it. We have two types of tasks: bugs and features/improvements.
I transform and decompose
Bugs are brought directly to the developers through the card system create by the tester, all improvements and features come through me. the business task of that will be understandable to the developer. In what form should the task come to Argentina B2B List me? It should contain answers to six questions. By running an idea through such a framework, it becomes clear whether it is worth the effort to implement. Where does this feature come from? How does it work? What effect does it bring.
Reading the technical specifications
How does it affect everything that happens in the game? What type/category of players is this aime at? What metrics might it affect? After, the developer should AERO Leads not only understand how the feature works, but also “see” it through the eyes of the user: how it looks, what happens when you click on this or that button, etc. Step by step describe all the mechanics and all the possible actions the user can take. When I was a junior and worke in a company where there were no other Unity developers, I receive general TORs without clarifications and details. It was very uncomfortable.
