Dreyfus model for the transition to a flexible work methodology

This material was written some time ago, and there are already more advanced models of the development of the team, but you can also learn a lot of useful information about the development path.

This article is useful if you want to learn more about how to create and use your own Dreyfus models.

What does a real agile team look like?

Start

• 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 about it with shareholders.
• We believe that we can not have time to deadline, and said this to your PM
• Flexible approach - really complicated stuff.

The first steps

• We are trying to deliver business 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 with it.
• Our mentor throws us good ideas.
• We highlight the person who deals with relations with foreign employees.
• We have a great business analyst who keeps close contact with shareholders.
• We know that we do not have time to deadline, our PM helps us
• A flexible approach requires considerable discipline.

Practicing team

• We know our software will work.
• Every two weeks we show working software to shareholders.
• We discuss with shareholders the following tasks that will be given to us
• We set a real deadline and are pleased that it was respected.
• We have our own good ideas.
• We quickly cope 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 overseas employees; we know who they are, what they look like, and communicate with them every day
• Our shareholders are really interested in the work we do.
• Before starting work, we always carry out testing, even if it is done manually.
• We know all the nuances of the implementation of our programs.
• A flexible approach is a very interesting thing.

Experienced team

• We work to meet deadlines.
• Sometimes we invite the CEO to his presentations to show 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 what we have learned new
• 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 non-working elements and identify changes that we will make to 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 the IT services are really interested in the work of our team.
• We regularly return to the previously used methods, as well as we are interested in the work of other groups.
• Working in a 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 are launching a new product every two weeks *
• Flexible approach - it's really easy if you know how to use it correctly!

')
* Well, this is the old model .