Developers Should Abandon Agile


40 bookmarks. First posted by ronnix may 2018.


Developers Should Abandon Agile -
from twitter_favs
23 days ago by fourstar
Developers Should Abandon Agile
from twitter_favs
12 weeks ago by leisa
“Agile”1 has become big business. Led, no doubt, by the Scrum Alliance’s successful Certified ScrumMaster offering, we now see hundreds, perhaps thousands of so-called “Agile” coaches and trainers, and many competing frameworks and methods. via Pocket
Pocket 
june 2018 by LaptopHeaven
learn to work this way:

Produce running, tested, working, integrated software every two weeks, every week. Build your skills until you can create a new fully operational version every day, twice a day, multiple times a day.
Keep the design of that software clean. As it grows, the design will tend to become complex and crufty. Resist and reverse this tendency consciously, refactoring in tiny continuous steps, all the time, so that your rate of progress is as steady and consistent as possible.
Use the current increment of software as the foundation for all your conversations with your product leadership and management. Speak in terms of what’s ready to go, and in terms of what they’d like you to do next.

This is the development team’s best hope for a reasonable life. By keeping the software always ready to go, we can hit any deadline with the best possible result. “Is today the deadline? Here’s what we’ve got, it’s ready to ship.”
programming  agile  scrum 
june 2018 by photoangell
No matter what framework or method your management thinks they are applying, learn to work this way:

Produce running, tested, working, integrated software every two weeks, every week. Build your skills until you can create a new fully operational version every day, twice a day, multiple times a day.
Keep the design of that software clean. As it grows, the design will tend to become complex and crufty. Resist and reverse this tendency consciously, refactoring in tiny continuous steps, all the time, so that your rate of progress is as steady and consistent as possible.
Use the current increment of software as the foundation for all your conversations with your product leadership and management. Speak in terms of what’s ready to go, and in terms of what they’d like you to do next.
agile  scrum  critique  project-management 
june 2018 by Mekk
Developers Should Abandon Agile
from twitter_favs
june 2018 by anorakgirl
Developers Should Abandon Agile
from twitter_favs
may 2018 by dvanlunter
This is RonJeffries.com, the combination of new articles, XProgramming, SameElephant, and perhaps even some new items never before contemplated. <br/>Copyright © 1998-forever Ronald E Jeffries
agile  criticism  scrum  programming 
may 2018 by gilberto5757
Developers Should Abandon Agile https://ift.tt/2G4FAPm
IFTTT  Feedly 
may 2018 by andytinkham
This is RonJeffries.com, the combination of new articles, XProgramming, SameElephant, and perhaps even some new items never before contemplated. <br/>Copyright © 1998-forever Ronald E Jeffries
agile 
may 2018 by geetarista
Other than perhaps a self-chosen orientation to the ideas of Extreme Programming — as an idea space rather than a method — I really am coming to think that software developers of all stripes should have no adherence to any “Agile” method of any kind. As those methods manifest on the ground, they are far too commonly the enemy of good software development rather than its friend.

However, the values and principles of the Manifesto for Agile Software Development still offer the best way I know to build software, and based on my long and varied experience, I’d follow those values and principles no matter what method the larger organization used.
xp  work  agile  scrum 
may 2018 by pjohnkeane