#feedback I’m no more doing Agile: therefore i am… or not ;-)

It’s been 10 months since i am no more doing SCRUM after almost 5 years being immersed on Agile Products/Software Development including 2 years leading as Scrum Master a Cloud Management product development team.

At this step of my road, i will take few minutes to make a feedback of my feelings and remarks regarding my old and new conditions:

Agile = global product awareness increased + code shared + skills acquisition increased + RUN/Support facilitated

Agile methods are really agile🙂 obviously this should be a fact but really it’s more easy to take in account products managers or customers needs on the flight.

  • Code shared ownership principle makes every body more aware of others features than in a waterfall project where the same guy is responsible of a piece of feature (almost) once for all and during months
  • Planning Poker and Specs global reviews let every body be aware of features and code
  • According to the previous points: RUN/Support is more easy to share as almost every body is bit aware of what this code is supposed to do. The fact that every morning every body can (not will) pick a task from another story shares the coding and therefore the knowledge
  • Easy product management due to native availability of management tool in Agile perimeter (Agile/Scrum board, Tasks and deadline tools, Daily meetings…)
  • Dev team can participate to the software design discussions and even being in charge (in my team some of use were architects and specifications writers)
  • To be the expert of a feature: you need to « reject » the fact to go on others or accept that the other way this will take some time. Personally i am more a full-stack guy so i will more likely go through participating at all layers/levels/features… to acquire the global view first
  • More is DevOps attitude🙂

Waterfall = specific feature expertise increased + developer direct responsibility of his feature + (normally) more solid specifications + more visibility (on product road map)

  • very quickly, being in charge of a piece of the product (given feature) make you take responsibility of this and force you to report of every dysfunction/bug
  • if this feature goes to production: you will be called to make support (that is good or bad regarding your expectation and willing to make support)
  • specifications almost come from the sky (even i am working in the Cloud this is not something good for me: just being dev is not my cup of coffee i want to design/architect and propose solution…)
  • customers needs don’t change every owner because there is a solid defined road map to target the best as possible (it could change on the flight obviously but not so frequently as in Agile)
  • more time to write and review the code
  • no direct integration test, the bugs detection comes more lately and should have to way for the next release or triggers a new hot fix delivery
  • there is more hot fixes than progressive releasing not meant to go in production (in my previous position only 1/2 releases goes to production)
  • The dev team is no more doing the demo (i like demos and being in charge of presenting our work. So that is disappointing to me)
  • no more time consumption activities that some devs hate (Poker, Daily meetings, Demos…)

DevOps fashion

Even in waterfall software development style, DevOps tendency is driving teams to adopt some agile manners:

  • continuous integration and continuous delivery are also evoke even the release cycle is not about 3/4 weeks but month at least
  • design taking operations/run in account is also bringing devs in the design
  • Agile team technical sessions/sharing is coming inside waterfall projects also as « dev and ops » sharing meetings –> security, architecture, performance… talks

Summary

Of course i prefer Agile/SCRUM (because of the fundamentals) but i am enjoying (yeah that is surprising me too) because inside a more rigid project management style as the waterfall is not the V cycle that it was: new tendency are bringing some « agility » inside.

Laisser un commentaire

Entrez vos coordonnées ci-dessous ou cliquez sur une icône pour vous connecter:

Logo WordPress.com

Vous commentez à l'aide de votre compte WordPress.com. Déconnexion / Changer )

Image Twitter

Vous commentez à l'aide de votre compte Twitter. Déconnexion / Changer )

Photo Facebook

Vous commentez à l'aide de votre compte Facebook. Déconnexion / Changer )

Photo Google+

Vous commentez à l'aide de votre compte Google+. Déconnexion / Changer )

Connexion à %s