• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Agile in Govt Contracting

 
Ranch Hand
Posts: 107
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Most of the work in my area is Government contracting. We have Scrum certification trainers come in and get a bunch of folks certified, but when you ask them real world questions they always answer "You aren't really doing Scrum". When you ask them who is really doing Scrum they answer "Spotifiy".

Going back to XP, most agile books assume that you are working on a utopian project where everyone has good will, the customer is not trying to pressure you to "do more with less", the project lasts forever, competitors aren't trying to take your work away from you.

What is the best way to be Agile in a Govt contracting situation?
 
Sheriff
Posts: 15801
264
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Paul Croarkin wrote:When you ask them who is really doing Scrum they answer "Spotifiy".


You should be aware that whenever people cite Spotify as an example, they're usually referring to what they read about Spotify, not what Spotify is currently doing. Like any good Agile organization, Spotify is constantly learning and adapting their practices. What Spotify is doing today is probably very different from what they did a year ago and probably will be very different from what they'll be doing a year from now.

If that kind of "inspect and adapt" behavior is what is being referred to, then yes, that's what Spotify does. But if it's more of a "Spotify does this and that and so on..." kind of like a recipe, then it's likely that recipe is obsolete and is not how Spotify actually does things any more.
 
Junilu Lacar
Sheriff
Posts: 15801
264
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I wrote:If that kind of "inspect and adapt" behavior is what is being referred to, then yes, that's what Spotify does. But if it's more of a "Spotify does this and that and so on..." kind of like a recipe, then it's likely that recipe is obsolete and is not how Spotify actually does things any more.


That's not to say you can't learn anything from what Spotify did at some point in their Agile adoption. You just need to be conscious about understanding whether the context in which they did those things and succeeded match the context you're trying to apply those same things. If your context is different from what Spotify's was at the time they did those things, the likelihood that you'll succeed is low or doubtful at best. As Andy Hunt likes to say, "Always consider context."
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic