Big Hairy Audacious Goal (BHAG)

Axel Arun
2 min readFeb 15, 2023

--

Why Is a Big Hairy Audacious Goal Useful?

A huge, hairy, ambitious goal is beneficial since it’s a long-term objective that all employees in a company can support. Built to Last: Successful Habits of Visionary Companies by Jim Collins and Jerry Porras is where the acronym BHAG, pronounced bee-hag, was first used. Simply said, a well-considered BHAG causes the attention to shift to the wider picture. It is intended to motivate and excite individuals in a way that long mission statements and quarterly targets frequently fail to, and if carried out correctly, can serve as the cornerstone for a remarkable accomplishment.

Agile Model

The Agile technique encourages ongoing communication between development and testing throughout the SDLC cycle of any project. The development and testing processes in the agile paradigm are concurrent, in contrast to the waterfall model. The agile technique promotes open communication between managers, developers, and testers.

For many firms, the agile development process and testing techniques have had great success. Agile’s advantages are openly acknowledged. They are particularly noticeable in workplaces. The following list includes some of the key agile model considerations:

  • Agile focuses on customer feedback, collaboration, and small and rapid releases.
  • Its purpose is to manage complex projects.
  • Agile produces better application suites with the desired requirements. Moreover, it can quickly adapt according to the changes made on time during the project life.
  • It has a small team size. Therefore, fewer people work on it so that they can move faster.
  • The agile model is not a suitable model for small projects. The expenses of developing small projects using agile are more than compared to other models.

Waterfall model

It is one of the easiest and most traditional models to manage. Because of its traditional development nature, each phase has specific deliverables and a review process. The waterfall model works well in smaller-size projects where requirements are easily understandable.

  • The waterfall model is not an ideal model to develop a large-scale project size.
  • The requirements in the waterfall model should be clear-cut at the beginning time; otherwise, it may lead to a less effective method.
  • In the waterfall model, it is hard to move back in order to make changes in the previous phase.

--

--