Establishing an engineering baseline is an iterative process and leverages a key tool to feed into its continuous improvement: Retrospectives.
Retrospectives are a great tool to improve what is not going well and keep or celebrate great aspects in a project. We found it very insightful as a team and a way to nicely end a project by revisiting the project stages and giving honest feedback about how we perceived them.
Visit End of project Retrospective | LinkedIn to read more about our learnings.
Currently, Sherryl Manalo is a Software Engineering Manager at Microsoft in the Industry Solutions Engineering (ISE) Organization. She leads multiple teams which engage with customers to build solutions running in the Microsoft Cloud. She has a Physics background and was in research before founding own start-up early in-career to build Open Source Solutions for customers. In 2008, she joined Microsoft and had various technical roles in the local organization before joining CSE in 2017. In her spare time, she likes going for a walk or riding her e-scooter, reading books, painting, cooking with her husband, hiking and skiing in winter.
At the end of a project or after a key milestone, we found it valuable to reflect on lessons learned as a team and see if some of our work could be useful to other Read more
This article is the fourth of a seven part series about habits of successful engineering teams. Part 1 was about healthy habits of engineering teams to facilitate team building and work well with each other. In Part 2, Read more
In part 1, I wrote about some healthy habits of engineering teams to facilitate team building and work well with each other. Part 2 was about having some key points in mind during the design phases to effectively Read more