Which is best approach (Agile or waterfall or Agile+waterfall)?
More so I have found Agile to be at best when developing an application that already exists and the constant enhancements and changes are made
I have been given a new Offshore assignment where the client is US based and most of the requirements and activities flow from Onsite to Offshore and expectations from Offshore (for which I am team lead) is to implement change requests, bug fixes etc. for the "existing project". So as obvious thing is that we need to work in a Onsite-Offshore model where we will have phone calls with onsite for clarification on requirements and most of our Offshore time is spent in communication itself (like writing mails articulating our problems, issues, clarifications etc.; phone calls, micro managing Offshore team as a Team Lead etc.) and to overcome communication challenges in implementing the change requests and clarifications required from Onsite in fixing the bugs in the existing application. So in this kind of environment, what do suggest for Offshore team to be productive ? what software development methodology do you suggest for Offshore ? do you suggest Waterfall or Agile ? any other tips for Offshore team without slogging at Offshore or spending long hours working at Offshore ?
Mary Poppendieck
Author of Lean Software Development, Implementing Lean Software Development, and Leading Lean Software Development
Akram Chotu wrote:I have been given a new Offshore assignment where the client is US based and most of the requirements and activities flow from Onsite to Offshore and expectations from Offshore (for which I am team lead) is to implement change requests, bug fixes etc. for the "existing project".
[OCP 21 book] | [OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
instead of clarifying the request, clarify what a clear request would look like, and insist that each request you get meets your needs
ICEfaces book . ICEcube . ICEfusion . Scrum
Mary suggests that you define criteria how a request "is written". Those criteria have to ensure that a request is understandable. You need rules that ensure that requests are written this way. So, you can reduce the amount of communication.
Mary Poppendieck
Author of Lean Software Development, Implementing Lean Software Development, and Leading Lean Software Development
Consider Paul's rocket mass heater. |