If teams are senior, there is a lure to run those review sessions not so often. And things are going well, since senior developers are using proper patterns and communicate together nicely.
The risk triggers when new teams appear and level of seniority is not proven yet. If system design reviews sessions are conducted once or couple of times only, there unpleasant surprises might pop up. Usually issues are experienced once components of those poorly designed systems are integrated. Velocity of new features development is struggling also.
Leverage the power of conversation, let people discuss the common approach in a structured manner. Do not let it go in uncontrolled manner.
No comments:
Post a Comment