Continuous Features

2019-12-29| Category: continuous coding| website:

There are numerous ways to define the feedback loop of planning. All of them have the same goal of generating the big picture.

As a Continuous Coder the how is less important than participating and speaking up if requirements and planning aren't clear. If you don't know why you are working on something, you will be less able to speak up and fix problems that only you are in a position to notice.

You may not have the authority, but you do have the responsibility.

How do you know which tool is best for the job?

  • Agile was designed to get small teams to iterate quickly. When is the best time to iterate quickly? When you are searching for marker fit, and seeking a solution which can go viral. This can be a startup, or an established company looking to spread.

  • In contrast, Six Sigma was designed for important critical systems which could cause disaster if they failed. When the company is already established and doing well, you don't want to harm the main source of income.

  • After a company has found a market fit, but before it's fully established there will be a period of chaotic and rapid growth. During this time, LEAN processes will help alleviate pressure while helping to learn which fires to focus on.

  • Like most techniques in Continuous Coding, none of these strategies will be enough on their own. They need to be paired with other techniques that fit the culture of the company best.

How does this apply to me as a developer?

  • Conway's law is most applicable during the feature definition phase of software development. This means that when practicing continuous coding, the language of the organization, and therefore the language of the variables and classes used within your code is going to be highly correlated to how features are organized.

    • For example, if you are working in a LEAN environment, your code will likely be set up as experiments, quick to throw away or be rewritten. If working in an Agile environment your code might be focused around UseCase Classes with the execute() function.

    • When using Domain Driven Design, you will have classes that reference repositories and boundaries.

    • Don't let the language of the domain scare you. They are all techniques with the same goals. Separation of Concerns, a common metaphor, and adaptability to change at the right level of abstraction.

Investment, Business


This site is a collaborative effort.
What do you want to see here?
Which articles are lacking or outdated?