Home / Lean Software Development

Our Tools

Lightweight tools for smart solutions

Ideal timeline for lean software development process
Like the lifecycle of building a baby, there are a sequence of indepedent stages to develop the full life cycle software product.

 Check out our guideline for transorming your ideas into requirements:
Requirement Specification Guide with Real-World EXAMPLES

Smart view for up-to-date information

Smart reporting - Data aggregation and data editing are on the same workplace (on the fly editing)
Add conversation or send inqury on the spot. Ease of discussion directly on spreadsheet instead of sending email back and forth.

Product roadmap: MosCow method is a cornerstone for planning a Minimum Viable Product.
The MoSCoW method is a prioritization technique used in management, business analysis, project management, and software development to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement; it is also known as MoSCoW prioritization or MoSCoW analysis.

Lean Product Roadmap

TIGOWAY: "Split and merge are critical activities to move fast in the sustainable manner."
There is a TIGOWAY, there is a lean solution.

TIGO RULE: "Keep it Simple, but Significant"

Key takeaways with man-month and ramp-up time

Example: Brook laws and increased communication overhead

The law is an "outrageous oversimplification". Below are the main factors that explain why it works this way:
  • It takes some time for the people added to a project to become productive. This is called "ramp up" time. Software projects are complex engineering endeavors, and new workers on the project must first become educated about the work that has preceded them; this education requires diverting resources already working on the project, temporarily diminishing their productivity while the new workers are not yet contributing meaningfully. Each new worker also needs to integrate with a team composed of several engineers who must educate the new worker in their area of expertise in the code base, day by day. In addition to reducing the contribution of experienced workers (because of the need to train), new workers may even make negative contributions, for example, if they introduce bugs that move the project further from completion.
  • Communication overhead increases as the number of people increases. Due to combinatorial explosion, the number of different communication channels increases rapidly with the number of people. Everyone working on the same task needs to keep in sync, so as more people are added they spend more time trying to find out what everyone else is doing.
  • Adding more people to a highly divisible task, such as cleaning rooms in a hotel, decreases the overall task duration (up to the point where additional workers get in each other's way). However, other tasks including many specialties in software projects are less divisible; Brooks points out this limited divisibility with another example: while it takes one woman nine months to make one baby, "nine women can't make a baby in one month".