Thought of penning down some of the issues I see with the projects where agile is tried via feeble mandate (lets just try it - top-down) rather than as a joint initiative between management and teams. The list will grow over time:
-->> Email being the preferred mode of communication rather than face to face communication
-->> Unwillingness to see the bigger picture by staying within the zone of "defined" responsibility
-->> Lack of communication on why we're doing it and how we want to do it
-->> Lack of training & coaching
-->> Unwillingness to try something different
-->> Unwillingness to understand new ways of working
-->> This is how we work, this is common sense, this is the only way it is practical!
-->> We will not touch the Engineering practices
-->> Unwillingness to share progress, impediments
-->> View that Agile is just an "iterative" waterfall
-->> Buffer resources for some reason, not made visible to customer
-->> Handling the fixed price contracts with variable scope is difficult
-->> Will not start the work till the SOW is signed/cost & scope are cast in stone
-->> Someone needs to prove that Agile will not cost more than what we are used to
Monday, November 2, 2009
Subscribe to: Post Comments (Atom)
14 Essential Software Engineering Concepts for Engineers and Managers
There are many terms and concepts that are important for an engineer to be familiar with, in order to effectively build software. This post ...
Alongboarding, an agile onboarding approach Alongboarding: We’re in it together! Organizations hire new people every day. A great first impr...
Consider This Someone is presenting the work that they have just completed. Compare and contrast the two scenarios below: ONE. "This is...
The Onboarding Canvas is a tool that can be used for onboarding a new team member . We derived this tool from Spotify's adaptation of ...
Post a Comment