Agile – Why its become a dirty word
There has been a lot of chatter recently on why agile is not the word it used to be. I offer a few bullets on why agile has in some ways become an off-roading term for software development based on bad practices I’ve seen:
- Scrum daily stand-up’s are really either status meetings or team meetings. Nobody in the team appears to recall the three standard questions to be answered, or the time-box duration for the meeting
- 12 original XP practices are often lost by agile teams. How often have you seen an agile team start coding with no coding standards, no design, and no idea of the XP practices on testing
- Using tools that restrict agility rather than enhance agility
- The perception that with a backlog, there is no need for requirements or non-functional requirements (NFRs) – this alone in my view is why backlogs seem to be the last item an agile team cares about, yet they are the core to the efficiency of an agile team
- Although most have agile/scrum/xp/etc on their resumes/CV’s, few appear to know the standard ceremonies of Scrum, and the reason for the ceremonies – backlog grooming is one that appears to be missing from many teams
- No wall 😦
Tales from a Trading Desk 
Agree 100% – although I think the bigger issue – or perhaps even one of the root causes of this is that there’s too much focus on the process and not enough on the philosophy. It’s really easy to understand _what_ you’re supposed to be doing during a Scrum event. It’s more difficult to understand _why_ – yet without the “why”, you’re just going through the motions.
I think Agile (the philosophy) and Scrum (a methodology) are intertwined in this post.
Hey! I just wanted to ask if you ever have any
trouble with hackers? My last blog (wordpress) was hacked and I ended up losing many months of hard work due to no data backup.
Do you have any methods to prevent hackers?
Nok et spennende blogginnlegg av deg! Liker bloggen din!
🙂