Our Approach

How we approach software development

Proven track record

Our approach has been effective and successful for over 25 years. Our track record for developing and delivering world-class technology solutions is proof that our approach works.

History

While CloverLeaf began in 1999, our principals and senior consultants have been delivering software development solutions since the early 1980's. Since that time, many different "industry standard" approaches to the software development life cycle have gone in and out of fashion.

Branded methodologies

Many large corporations have their own "branded" methodology — usually some variation of existing approaches. Even today there are a number of different software development methodologies in vogue.

Adhering to a methodology

If a methodology is blindly followed without considering the size, complexity, and resources of a project, the results will not fit the needs. This can mean that effort spent managing the project is greater than the value provided by that effort. We consider each project separately and apply our methodology as required.

Controlling structure

We understand the importance of structure and strive to apply only what is necessary. Many projects become bogged down by the size and complexity of their structure. Larger projects typically require more structure than smaller projects. Projects involving complex business problems typically require more structure than simple ones — regardless of the size.

Bottom Line: CloverLeaf favors Agile*

We favor the Agile approach because we have been practicing its principles and philosophy long before it had a name.


*While CloverLeaf definitely leans toward the Agile approach, we recognize that some elements may or may not be appropriate depending on the business problem and/or client standards.

Agile Principles*

  • Customer satisfaction by rapid, continuous delivery of useful software
  • Working software is delivered frequently (weeks rather than months)
  • Working software is the principal measure of progress
  • Even late changes in requirements are welcome
  • Close, daily cooperation between business people and developers
  • Face-to-face conversation is the best form of communication (co-location)
  • Projects are built around motivated individuals, who should be trusted
  • Continuous attention to technical excellence and good design
  • Simplicity
  • Regular adaptation to changing circumstances

*Reference: Agile Software Development