Loading ...
Sorry, an error occurred while loading the content.

56235Re: [scrumdevelopment] Re: Well done waterfall+agile

Expand Messages
  • George Dinwiddie
    Nov 16, 2012
    • 0 Attachment

      On 11/16/12 10:51 AM, jerzyklek wrote:
      > Hi,
      > I am quite new to this and and have been lurking for some time.
      > I have one question to this comment since I am in a bit similar
      > situation: we have a huge backlog of things which all
      > are wanted by some customers, prioritized by the customer importance,
      > and usually we can go through quite a few sprint before something new
      > gets into the backlog on top of it, having a higher priority.
      > I also understand that Agile emerged in places where the customer did
      > not know what he/she wanted,

      I suggest that your understanding is not quite correct. Perhaps
      sometimes, but that's not the general case. More commonly, the customer
      DID know what they wanted, but were able to take advantage of things
      learned during development to achieve something better or sooner.

      > and main impact of "learn and adapt"
      > principle on project success was by enabling the result of one
      > iteration/sprint to influence the remaining product backlog.
      > We don't have much of that, but sprint reviews allow us adapt our
      > ways of working on a team level: how we plan, estimate, test... what
      > we document and so on... I think it's another aspect of "agility": we
      > do not adapt the backlog, but adapt our ways of working. Not "fully
      > agile" then, but still a bit.
      > I am pretty sure that out POs could use the reviews more to our
      > benefit, but anyway...
      > //Jerzy
      > --- In scrumdevelopment@yahoogroups.com, George Dinwiddie <lists@...> wrote:
      >> Marco,
      >> On 11/8/12 7:00 PM, marcodorantes wrote:
      >>> Hi all,
      >>> I am looking for articles or papers that talk about the details of
      >>> how to successfully execute a development project with a waterfall
      >>> façade to the upper-management layer and an agile approach for the
      >>> development team. All is new in the project: the team, the users, the
      >>> application, the technology. Note that with «waterfall» I mean strict
      >>> sequential stages of requirements, analysis, design, coding, testing,
      >>> deployment to production, and three months of maintenance; along with
      >>> a fixed-price/fixed-scope contract, and a single Gantt chart as part
      >>> of the signed contract. This Gantt chart will work as the criteria
      >>> for payments at the end of each stage against stated deliverables in
      >>> the contract.
      >>> I have heard, from time to time, that some teams have done precisely
      >>> that and very well done. Yet, I have not checked the evidence to
      >>> believe it.
      >>> Could you point to those articles or papers, or experiences?
      >> I've seen a number of teams who think they're doing Agile development,
      >> but are, instead, trying to burn through a fixed backlog by using
      >> iterative processes. Theoretically, that could work. It would even give
      >> you a better indicator of progress (or lack of it). I've never seen it
      >> go well, however. It has all the fragility of waterfall plus the
      >> frustration of not being allowed to use what you learn as you go.
      >> If you can't change the backlog, it's not, by any means, Agile under the
      >> covers. It's still waterfall, even if you use some practices that are
      >> commonly associated with Agile.
      >> - George

      * George Dinwiddie * http://blog.gdinwiddie.com
      Software Development http://www.idiacomputing.com
      Consultant and Coach http://www.agilemaryland.org
    • Show all 27 messages in this topic