What, How, and When in Software Development
In the realm of software development, navigating the intricate balance between the “What,” “How,” and “When” is akin to orchestrating a symphony. Each element plays a crucial role, and the success of a project hinges on the clarity of ownership and collaboration between business and technical functions.
Trouble often brews when lines blur, and the wrong entity assumes control over decisions. The pitfalls are evident when business stakeholders delve into the technical intricacies (“How“) or technical teams embark on defining end-user features (“What“) without engaging users or considering business needs. Dictating the “When” without due consideration for the “What” or “How” spells trouble.
A common scenario unfolds when a business leader asserts, “It’s obvious what needs to be done—why can’t they just start coding?” This presumption that the “What” is self-evident implies a potential lack of understanding of both the “What” and the “How.” If such directives are enforced without clarity, projects often veer off course, and blame tends to fall on the engineers.
Projects thrive when responsibilities align: the business defines the “What,” engineers articulate the “How,” and both collaborate on determining the “When.” Flexibility is key, especially when external factors like trade shows or investor deadlines fix the “When.” In instances where the “How” or “What” is inflexible, negotiations must focus on the remaining variables.
Attempting to monopolize all three aspects—dictating the “What,” “How,” and “When”—is a precarious endeavor. Even visionaries like Steve Jobs and Elon Musk recognize the value of delegation and trust in their core engineering teams. Attempting to outsmart such seasoned leaders should prompt a moment of reflection.
Communication emerges as a linchpin in this dynamic. The clarity of the “What” and “How” relies on effective expression, be it in backlog elaboration or technical documentation. A seemingly clear vision may reveal gaps during the collaborative process. The call to “just start coding” often underscores a misunderstanding of how successful projects materialize, emphasizing the need for detailed articulation.
While verbal communication and whiteboard sessions can expedite the process, the inclusion of insights from those executing the work enhances the quality of the backlog and accuracy of timelines. Appreciating the distinct value of each component— “What,” “How,” and “When”—coupled with acknowledging the rightful owners, forms the crux of a successful software development recipe at AmBrightTech.