| By Udayan Banerjee |
Article Rating: |
|
| September 10, 2012 02:47 AM EDT |
Reads: |
973 |
Trust – you can be sure that without it agile will not work.
Change in requirement involves rework and it may imply discarding work already done. If IT believes that the change is due to carelessness or inefficiency of business then the result would be acrimonious.
Similarly, there are features which look simple from outside but are complex from inside. If business believes that IT has unnecessarily inflating the estimate than it would have same acrimonious result.
On the other hand if IT believes that the change is needed and could not be specified earlier and business trusts the estimate provided by IT then you improve the level of trust between IT and business.
When the work has been outsourced then this problem becomes even more prominent.
These situations and not new and traditional heavyweight methods were build assuming such problems exist.
Agile assumes that such problem can be overcome through trust.
But, how to move to a position of trust? Would trust develop if you implement agile? Or, would it be necessary to build the trust before attempting agile?
Udayan Banerjee on Google+
Related Posts
Udayan Banerjee is CTO at NIIT Technologies Ltd, an IT industry veteran with more than 30 years' experience. He blogs at http://setandbma.wordpress.com.
The blog focuses on emerging technologies like cloud computing, mobile computing, social media aka web 2.0 etc. It also contains stuff about agile methodology and trends in architecture. It is a world view seen through the lens of a software service provider based out of Bangalore and serving clients across the world.
The focus is mostly on...
- Keep the hype out and project a realistic picture
- Uncover trends not very apparent
- Draw conclusion from real life experience
- Point out fallacy & discrepancy when I see them
- Talk about trends which I find interesting
Google
Subscribe to SOA World Magazine Email News Alerts
Subscribe via RSS
