Dreyfus model for transition to a flexible work methodology

Original author: Dave Grant
  • Transfer
This material was written some time ago, and there are more advanced models for the development of the team, but you can also get a lot of useful information about the development path in it.

This article may come in handy if you want to learn more about how to create and use your Dreyfus models.

What does a real Agile team look like?


  • We have a board
  • We write assignments on the board
  • Every two weeks we get together and celebrate what we have done
  • Sometimes we talk with shareholders about this.
  • We believe that we may not be in time for the deadline, and we told our PM about this
  • A flexible approach is really hard

First steps

  • We are trying to supply working software.
  • We are trying to use the experience of previous projects to find out what was bad in the past.
  • If something does not work, we ask the mentor to clarify what to do about it.
  • Our mentor throws us good ideas
  • We highlight a person who deals with relations with foreign employees
  • We have a wonderful business analyst who maintains close contact with shareholders.
  • We know that we will not be in time at the deadline, our PM helps us
  • A flexible approach requires considerable discipline.

Practicing team

  • We know that our software will work
  • Every two weeks we show working software to shareholders.
  • We are discussing with the shareholders the following tasks that will be assigned to us
  • We set a real deadline and are satisfied that it has been respected.
  • We have our own good ideas.
  • We quickly deal with difficulties.
  • We write one-time automated testing programs
  • We write acceptance tests
  • We are trying to use the experience of previous projects to find out what prevented us from creating software.
  • Before starting work, we always know what the final product will look like.
  • We love our foreign employees; we know who they are, how they look, and we communicate with them every day
  • Our shareholders are really interested in the work that we do.
  • Before starting work, we always carry out testing, even if it is done manually
  • We know all the nuances of the process of implementing our programs.
  • A flexible approach is a very interesting thing.

Experienced team

  • We work to meet the deadline
  • Sometimes we invite the CEO to our presentations to demonstrate to him that the flexible approach is being implemented quite successfully
  • People applaud us at the end of the presentation, everyone is very happy
  • The screen displays the work of a foreign team; we can chat with them at any time; they can also see us
  • We are trying to use the experience of previous projects to find out that we learned new things.
  • We test our mentor and change working methods in such a way as to work more successfully.
  • Before starting work, we always carry out testing, even if it is done manually, to diagnose inoperative elements and determine the changes that will be made by us in the source material
  • A flexible approach can be applied not only to software development

Team of specialists

  • We attend conferences and discuss with colleagues the experience of using a flexible approach.
  • We help other teams
  • Many outside IT are really interested in our team.
  • We regularly return to previously used techniques, and are also interested in the work of other groups.
  • Work in the company is interesting and innovative.
  • Companies need to try different approaches and get quick feedback.
  • We never have to work overtime or on weekends.
  • We launch a new product every two weeks *
  • A flexible approach is really easy if you know how to use it correctly!

* Well, this is an old model .

Also popular now: