But Emotional Retrospective: The importance of planning
Last week, I developed Lambda functions on AWS. I made 7 functions and each function was responsible for the corresponding API. Lambda functions' role was relaying an HTTP request to a 3rd-party server, storing the process result and responding with it. In short, each lambda function is functioning as an API service.
From the whole project, my role is developing the backend side of the project. This week was the first sprint. My manager told me to complete the basic development by the end of the sprint. Basic development means that APIs are exposed so that Web developers could build the web pages. It doesn't have to be fully functioning. But It should be able to guide Web developers on how to build the web site.
Goal
- Make running lambdas in accordance with spec document.
Sprint
- Start date: Monday
- Due date: Friday
What I did
-Monday: learn how to use Lambda, search about pooling with Lambda
-Tuesday: add a basic handler and 5 other handlers.
-Wednesday: add Http Client.
-Thursday: add RDS with HikariCP connection manager.
-Friday: add return codes, handle exceptional cases.
-Everyday: develop business logic and update codes according to the changes in the document.
What I should've done
- SCHEDULING!
I spent the whole week doing randomly. ( like greedy algorithm )
This is the worst habit.
Planning is the first thing I should do and it's all.
No plan means having a failed plan.
It doesn't matter how big is a scalar if a vector is wrong.
A retrospective is meaningful only if there was a plan.
Emotional retrospective doesn't help.
No retrospective means no improvement. ( both personally and professionally )
I can make a plan means I can estimate time and it means I can arrange tasks specifically and it means I can analyze what the problem is and it means I know what I know and what I don't and it means I can see my self in a detached way and it means I am sorted out.
From the whole project, my role is developing the backend side of the project. This week was the first sprint. My manager told me to complete the basic development by the end of the sprint. Basic development means that APIs are exposed so that Web developers could build the web pages. It doesn't have to be fully functioning. But It should be able to guide Web developers on how to build the web site.
Goal
- Make running lambdas in accordance with spec document.
Sprint
- Start date: Monday
- Due date: Friday
What I did
-Monday: learn how to use Lambda, search about pooling with Lambda
-Tuesday: add a basic handler and 5 other handlers.
-Wednesday: add Http Client.
-Thursday: add RDS with HikariCP connection manager.
-Friday: add return codes, handle exceptional cases.
-Everyday: develop business logic and update codes according to the changes in the document.
What I should've done
- SCHEDULING!
I spent the whole week doing randomly. ( like greedy algorithm )
This is the worst habit.
Planning is the first thing I should do and it's all.
No plan means having a failed plan.
It doesn't matter how big is a scalar if a vector is wrong.
A retrospective is meaningful only if there was a plan.
Emotional retrospective doesn't help.
No retrospective means no improvement. ( both personally and professionally )
I can make a plan means I can estimate time and it means I can arrange tasks specifically and it means I can analyze what the problem is and it means I know what I know and what I don't and it means I can see my self in a detached way and it means I am sorted out.
Comments
Post a Comment