Timeline for Is agile about development or management?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 25, 2012 at 16:42 | comment | added | Tim | @pdr Well he's definitely agile, he just doesn't follow any agile development process that we would adhere to. But perhaps it's more talking about "Agile" the noun, i.e. the process that's a bit like Scrum, that irks me most. | |
| Sep 25, 2012 at 16:35 | comment | added | pdr | @Tim: I had a phone interview once where I asked to what degree the interviewer thought they were Agile and he went on to tell me that they had to be because the business changed their minds on a daily basis. Couldn't argue his point in that they had to be agile, but that's not being Agile. So no, I think the distinction is important. | |
| Sep 25, 2012 at 16:29 | comment | added | Tim | Am I the only one who doesn't think "agile" should have a capital letter? I'm not just being a grammatical pedant - it's important. Understand agility as a quality: if your team is agile, it is flexible, adaptable, methodical. I always find confusion starts when they talk about "Agile" as if it's the name of a standard pattern or process to which they must adhere. | |
| Sep 25, 2012 at 16:29 | comment | added | Ashkan Kh. Nazary | @pdr (and others ;-) ) May I bring your attention to programmers.stackexchange.com/questions/166156/… | |
| Sep 25, 2012 at 16:19 | comment | added | Jimmy Hoffa | @ashy_32bit I would say the scrum master will help the team become more rigorous and affective in following a good process, but the veteran XP coach will help the team become more rigorous and affective in writing good code. Based on your description of the team, I'm guessing they could use help writing better code if they have never written any tests before. They probably don't write very loosely coupled code or pay attention to design principles etc in that case. Granted your hypothetical team is also clearly bad at process too. | |
| Sep 25, 2012 at 16:14 | comment | added | pdr | @ashy_32bit: Which problem most needs solving? Project management or development? Does either need solving? | |
| Sep 25, 2012 at 16:11 | comment | added | Ashkan Kh. Nazary | @pdr Just to clarify let's continue with my imaginary team: They are about 20 developers, they have heard about agile, TDD and stuff but not a single test suite in their product. The company is trying to choose to spend a good fortune on 1) A certificate holding Scrum master 2) A veteran XP couch Which option best serves the team ? | |
| Sep 25, 2012 at 16:08 | comment | added | Jimmy Hoffa | +1 Thankyou pdr, it frustrates me to no end that everyone says agile and means scrum, which ends up obscuring the good of the actual agile principles because everyone thinks agile means daily standups and sprints and never learns about the manifesto. | |
| Sep 25, 2012 at 16:08 | comment | added | pdr | @ashy_32bit: Not a question anyone can answer without knowing the team and the project. Not every team or project would benefit from Agility. However, I have worked on a team that was doing Scrum and CI and nothing else (from the Agile box of tricks) and it worked better in that case than doing neither of these things. But we sought to improve our Agility over time. | |
| Sep 25, 2012 at 16:04 | comment | added | Ashkan Kh. Nazary | I see. Quite insightful but I'm still confused over some points. For example is it beneficial to implement Scrum on a development team that is not doing agile on the programming side ? | |
| Sep 25, 2012 at 15:55 | comment | added | user40980 | agilemanifesto.org/principles.html elaborates on the manifesto. | |
| Sep 25, 2012 at 15:53 | history | answered | pdr | CC BY-SA 3.0 |