#agileprogramming

[internet-and-society-blog]

Agile programming was originally a tech development process, created to fix the ineffective process of most businesses. It was designed to break the development process into small chunks that would either succeed or fail quickly to save time from being spent on a project that would eventually fail. Bruce Feller adapted this technique into an agile manifesto to help families run smoother. There are three main parts:

1. adaptability: this is necessary because you can't predict everything that might happen, and adaptability allows one to react in real time. An example is having family breakfast instead of dinner if there is a conflict at dinnertime.

2. Empowerment of children:by giving children a say in their own development, they get practice in independence which is an ultimate goal of parenthood. An example of this is having children be in charge of their to-do list, as my artifact shows.

3. Sharing your story: by defining your core values as a family and telling your children about their family history, it gives children a higher self-esteem and makes them happier. An example of this is family meetings.

This concept of parenting relates to the effect of the new media on family life, as this technological concept has been adapted to form a parenting concept.

This topic is approached from a utopian perspective, where agile development is being hailed as the solution to making a happy family, and it has strong case arguments to support it.

[patnoble]

At the heart of Eric Ries's "The Lean Startup" is a simple idea: the products a startup builds are really experiments. From that provocative starting point, his book advances a novel framework, founded in the lean manufacturing and agile programming movements, for turning product and service ideas into sustained innovations. At the heart of his thesis is the argument that building sustained long-term change requires immediate experimentation and continuous, incremental improvement, moving as quickly as possible through successive Build --> Measure --> Learn development loops. The framework emphasizes driving to the build phase rapidly by focusing on a minimum viable product to be tested with early adopters in decisive split-test experiments. These experiments should produce clear, actionable, baseline metrics – as opposed to "vanity" metrics – that permit validated learning, allowing entrepreneurs to make the key decision to persevere or to pivot in the direction of a new strategic hypothesis. In practice, however, implementing the loop above actually requires reverse planning: figure out what needs to be learned, use innovation accounting to figure out what needs to be measured to know if validated learning is occurring, and then figure out what minimum viable product needs to be built to run that experiment and get that measurement.