We only ship to addresses in the USA. Live somewhere else? Please order from one of our international distributors. Click Here
Product added to carts.
BK Blog Post
As you probably know, agile does not have its own methodology. On the other side, it can be defined as a combination of other methodologies. Scrum has, for example, its own methodology. All of these are, of course, connected and make a unity.
The main difference between project management and agile training is the way the work is done. In the project management, the goal is the only thing that is important. In other words, the deadline and the delivery itself, those are priorities.
When it comes to agile training preference is slightly different. The agile team has a focus on the manner things are done. The whole process is evaluated by each segment of it. The delivery is important, but the steps which lead to it are weighty, sometimes even more than the result.
This all had to start somewhere. So, here’s the story…
We can say this is the Bible of agile. In this Manifesto (2001) main values are defined by people who agreed to this Manifesto at first. Some values have more significance than the others. Insisting on the technical acts is not supported in this document. It is bringing an individual in the focus and the need for adaptability.
This speaks enough about the approach and why is agile highly desirable among the team members. Its working method is positive and tries to bring out the most successful outcomes of every software development. The team members are lead by the thought they can’t make a fatal mistake or get a penalty for it, that time they invested in the project will be appreciated, that their opinion and attempts will be more important than the documents etc.
Best practices in practice
The highlight here is the interaction between the members. They are united in completing this project, dedicated to it, with a positive mindset. The trust given to them can be a great motivator and can bring out the best of them and the extraordinary results.
The mixture of old, checked techniques and new ones is the best option. Secondly, a mixture of practices and applying another practice type to another team is completely okay. Now the adaptability expresses itself. There is no a model which can be applied to every case, this is too rigid.
The best way to get the team member fully trained and practiced is to show them a couple of possible approaches, then take out the best in each an make a completely new model.
Agile training and agile practice should be adapted to the team’s culture or the job needs. There is almost no example of an agile practice that repeated itself. Many similarities can occur, but as each team has some special needs and characteristics, practices have to be very flexible.
If you work with a good partner, you can try to come up with a solution for the practice. To be a real representative of agile training and practices, one must have all those attributes agile represents. So, we must repeat, flexibility is the key.
Sometimes a person who is the representative of agile training doesn’t have a complete image of the team they are working with. This is the time when first signs of agility appear. The team members should introduce or annex some important material in order to come up with the best possible practice. They know themselves best.
Last but not least thing is discipline. Challenges are present in each software development process, so be ready for it. If you know in advance what to expect, don’t allow yourself to fall back after a fail. Have a strong spirit and always remind yourself of the Manifesto values.
Nothing bad even if a part of the practice is rejected as it is not suitable. Keep on working on the rest of the practice, add up those missing parts and the results won’t trail.
Thanks for the Agile Course.