Manifesto

The AgileConstellation Manifesto is the summary of the analysis work done in the domains related to complex solutions, going to highlight the fundamental aspects related to the governance, risk and sustainability of the initiative.

 

PHILOSOPHY

The AgileConstellation philosophy is the same as the renaissance workshop onethe cell where everything needed was made to realize a new handiwork: starting from the design to the marketing, going through the learning and the production.

Team’s members are pushed to behave like renaissance craftsmen, with ability they use various materials, techniques and tools to satisfy the handiwork’s customer.

AgileConstellation brings the customer’s need to the center, harmonizing competencies, approaches and various technologies by defining a main-set of market economically-sustainable solutions.

 

PRINCIPLES

It’s not about the individual part: it’s about jobs to be done!

It’s not the completion of components and then the related, rather the focus is on a smart solution to solve a need in an effective and efficient way.

 

Think less and do it!

Reduce to the bare minimum the time dedicated to the analysis phase, in favor of a quick startup of development’s activities related to the solution.

 

Simple is better!

Simpler is the solution, more chance we have to evolve it according to stakeholders needs.

 

If you can’t remember it, you can’t improve it!

Using visual management system to monitoring the state of the solution development.

 

PRACTICES

fast prototyping rev 120

Fast Prototyping 

 The goal of the Fast Prototyping is to validate the overall sustainability of the solution.

The sustainability is characterized by 5 bubble-aspects that focuses on the main ones, related to the enterprise solutions: 

  • People: focused on the interaction between the involved people, their way of working and the related tools;
  • Artifacts: focused on the rapid validation of the artifacts affecting the product;
  • Security: focused on the verification of the security aspects, which affect the realization of the solution;
  • Legal: focused on the analysis of the law and regulations, national and international, which the solution must consider;
  • Delivery: focused on the analysis of the delivery related to the various elements that compose the solution, as well the whole solution itself.

Furthermore, depending on the specific domain, more bubbles can be added to specify specific elements to be assessed for verify the sustainability.

All this bubble-aspects explicitly contribute to the evaluation of the solution cost/benefit.

 

Make-Measure-Learn

The Make-Measure-Learn (MML) loop aims to fast experiment different hypotheses and assumptions:

  • Make: create a prototype to test the Vision assumptions and starting to consolidate the reference team;
  • Measure: analyze the prototype according to the Goals and related metrics. Also check whether the organization and the team are confident with the solution creation;
  • Learn: adopt the necessary changes depending on the results.

 

Flashback

The so-called flashback leads the team to match the state of the solution with a fast alignment, where the observer team will check the work of another team directly. During this action the observer team can ask a limited number of questions in a short timeline.

The flashback may reveal the need to investigate some aspects, which leads to a Review Blitz in which to resolve any doubt.

 

Continuous Improvement 

The goal of the Continuous Improvement is to reduce to the minimum the interventions on the least flexible aspects of the solution. The approach is to act on the reasonably modifiable elements, in order to constantly improve the overall solution.

 

Continuous Integration

The Continuous Integration pushes the team to integrate continuously (and as soon as possible) every change, in order to identify problems and resolve them in a timely fashion.  This helps to reduce the costs associated to the unexpected behaviours.

 


All the elements described in the guide are the result of direct experience and many discussions with experts, coming to extract the essence of complexity that a new initiative brings with it, both from a technical and organizational point of view.

The guide is a "pretotype", to represent a constant and evolving work depending on the field of application of a new applications. In this sense, the suggestion is to use the guide as a reference in the context of your own reality according to you own corporate culture.