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 collaborate as a team. This article, which is the third of a seven-part series, is about useful habits of Engineering teams while working on the backlog.
I’m not re-iterating Agile methodologies here, and I’m also not claiming to be an expert in Scrum, Kanban, Lean, etc. Take these ramblings as me sharing experiences we had in several projects while applying Agile methodologies and processes in different flavors. Perhaps you also had this experience and can relate, or you know of a better way. In this case, I’m genuinely interested in learning more from you.
It’s great to have a process to follow and a framework everyone is experienced in. It doesn’t need much onboarding and explanation for the team as a certain baseline already exists regarding collaboration. If the project team hasn’t worked with each other before, ideally the differences in perception and expectations are only slight deviations from a specific methodology.
