Transferring AGILE principles to non-development teams

Raven young’s Blog has a post which links to Transferring AGILE principles to non-development teams. Thanks to Raven for Posting it.

The post talks about four Agile principles which are particularly useful for teams, managers, and team leaders.

  • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  • Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  • Simplicity–the art of maximizing the amount of work not done–is essential.
  • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

In my opinion building projects around motivated individuals is a key thing. Unless you have a team of motivated individuals its very tough implement agile principles in any organization.

If the design is simple and open for changes, then the second one will happen. Most of the team members are not ready for this. People still talk about what if a requirement changes in a second phase of the project. We are so much habituated to the waterfall kind of development, its very touch to change the mindset of the team. Training and mentoring people plays a key role here…

Link to the original article

Worth Reading….


Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s