Skip to main content

An Interest in Lean Startup Approach?

[PLACEHOLDER]
Image property Beolle Blog

That moments when we have that “idea” and get yourself excited believing that it will be your big break. This gets us thinking about “starting” a project and possibly building a business. This is a great feeling and it is part of the creative process. However the “passion” should be combined with a methodology, a framework, a tool that can help us evaluate, guide and measure the progress in order to build and make your dream a reality.

There are several school of thoughts that we can study and even combine together to plan for our entrepreneurial endeavors of building software products and/or services that we have envisioned.

One approach that I found very interesting in the product development business is the concept of “Lean Startup”. Below are a few points that got me interested in this subject (if you are looking for an introduction or find more info I encourage you to follow the links in our reference section), all elements part of the “Lean Startup” approach:
  1. The tough and important questions that we should ask ourselves: “Can this product be built?” vs “Should this product be build?”
  2. The concept of Minimum Viable Product (MVP): a product that has the core features that allows the product to be deployed. You can see it as a strategy to have your product available to a subset of customers in order to get feedback. It is part of an iterative, prototyping process. 
  3. Involve measurement and learning and actionable metrics that can demonstrate cause and effect questions.
  4. The use of the “5 why’s”. The intention is to attack the problematic items of the idea. It is an investigate method based on asking the question “why?” five times for understanding the root cause of the problem. 
  5. The “Lean Startup” has 5 principles. 2 of them I found it very:
    • 3rd principle -> Validated learning: “Startup exists not to make stuff, make money or serve customers. They exist to learn how to build sustainable business. This learning can be validated scientifically by running experiments that allow us to test each element of our vision”.
    • 5th principle -> build – measure – learn: “Fundamental activity of a startup is to turn ideas into products, measure how customers respond and then learn whether to pivot or persevere. All successful startup processes should be geared to accelerate the feedback loop”.
So if you are looking to build something then remember to use a method that helps you organize, measure and get feedback. Keep it simple and "fail-fast and often". Perhaps take a look at the "Lean Startup" and see if this method can fulfill the needs of your startup.

Reference:



Trending posts

Apple's App Tracking Transparency sealing Meta's fate

If you have been following the recent news on Meta (formerly Facebook) you may have read that Meta recently projected their ad revenue will be cut by a staggering $10 billion in 2022 due to Apple’s new App Tracking Transparency feature (also known as ATT). This has resulted in Meta’s stock to plummet by over 20%. Photo by julien Tromeur on Unsplash - modified by Beolle So what is Apple’s ATT and how does it impact ad revenue? Apple has been releasing multiple privacy features for the last few years. This included Apple’s Mail Privacy Protection and Apple’s App Tracking Transparency feature. You can learn more about Apple’s Mail Privacy Protection in our earlier post by clicking here .  Apple’s App Tracking Transparency (ATT) was launched in iOS 14.5 and iPadOS 14.5 where it prompted users to select if they wanted the app to track their activities across other apps on the device. The prompt is displayed when the user opens an app like Facebook or Instagram for the first time o...

Assembling MLOps practice - part 2

 Part I of this series, published in May, discussed the definition of MLOps and outlined the requirements for implementing this practice within an organisation. It also addressed some of the roles necessary within the team to support MLOps. Lego Alike data assembly - Generated with Gemini   This time, we move forward by exploring part of the technical stack that could be an option for implementing MLOps.  Before proceeding, below is a CTA to the first part of the article for reference. Assembling an MLOps Practice - Part 1 ML components are key parts of the ecosystem, supporting the solutions provided to clients. As a result, DevOps and MLOps have become part of the "secret sauce" for success... Take me there Components of your MLOps stack. The MLOps stack optimises the machine learning life-cycle by fostering collaboration across teams, delivering continuous integration and depl...

AGILE For DIGITAL AGENCIES

Introduction Some Digital agencies have a project process where waterfalls still plays a big part of it, and as far as I can tell, the tech team is usually the one suffering as they are at the last part of the chain left with limited budget and time for execution. I do believe that adopting an Agile approach could make a Digital Agency better and faster. In this article I’m presenting you just another point of view of why it make sense looking at Agile Methodology.  Why Agile for a Digital Agency? The Agile movement started in the software development industry, but it has being proven to be useful in others as well. It becomes handy for the type of business that has changing priorities, changing requirements and flexible deliverables. In the Digital Agency of today you need a different mindset. Creative will always play a huge role (“the bread and butter”). But the “big guys” need to understand that without technology there is no Digital Agency. Technical resources ...

SLA-SLO-SLI and DevOps metrics

Companies are in need of the metrics that will allow them to stay in business by making sure they meet the expectations of their customers. The name of the game is higher customer satisfaction by winning their trust and loyalty. To do so, you want to provide good products and services. Therefore you need to find ways to monitor performance, drive continuous improvements and deliver the quality expected by the consumer in this highly competitive market. Photos from AlphaTradeZone via Pexel and Spacejoy via Unsplash SLAs, SLOs and SLIs are a good way to achieve the above. They allow clients and vendors to be on the same page when it comes to expected system performance. If we go one level deeper, vendors/providers work on NFRs (Non-Functional Requirements) when working on their solutions. NFRs define the quality attributes of a system. I bring them up because the relationship between them and the SLAs is that they provide, in a way, foundational aspects for the SLA-SLO-SL...

This blog uses cookies to improve your browsing experience. Simple analytics might be in place for pageviews purposes. They are harmless and never personally identify you.

Agreed