Timeline for Senior developers 'reject' agile. What now?
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 17, 2021 at 15:50 | history | edited | Samuel Muldoon | CC BY-SA 4.0 |
I wrote an answer; someone did not like my answer, so they deleted half of what I wrote. If you don't like my answer, go write a different answer, or downvote my answer. Do not delete half of my text. Some of the changes were okay, but I put back most of what was deleted.
|
| Jul 15, 2021 at 16:43 | history | edited | Sarov | CC BY-SA 4.0 |
Remove potentially-offensive content
|
| Jul 12, 2021 at 13:47 | comment | added | Sarov | As an aside, Scrum is not an acronym, thus there's no reason to put it as 'SCRUM'. | |
| Jul 12, 2021 at 13:37 | comment | added | Sarov | My concern is that your answer appears to run afoul of the be nice guidelines. I don't mind you holding a different opinion than me, but as someone who uses Scrum terminology, I don't appreciate the statement that I am "[probably] incompetent, [with] nothing [to] say [that] is actually insightful". As such, my earlier comment. If that was not your intent, please edit to clarify. If it was your intent, your answer may be flagged for deletion as 'rude or abusive'. | |
| Jul 12, 2021 at 13:37 | comment | added | Sarov | While I don't agree (using proper terms can be used to both avoid confusion and for convenience - which is better: "hand me the thing with a handle, a long metal shaft, and four nubs on the end" or "hand me a Phillips screwdriver"? Sure, it's more confusing if they don't know what a Philips screwdriver is, but that's why you need to know your audience. To suggest to never use the term 'Philips screwdriver' because some don't know what it means is absurd), that's not what I commented about. There's nothing wrong with posting an answer others may not agree with. | |
| Jul 10, 2021 at 18:28 | comment | added | Samuel Muldoon | @Sarov Are you able use SCRUM without use SCRUM terminology? If not, then you have invented a made-up language, not a set of effective business practices. Whether you have experienced and inexperienced software developers work in pairs or not is language-independent. Also, you can have an engineering team talk about the project once per day or once per week, all without inventing new words to describe such things. If You were to watch a movie of your team working with the MUTE setting turned on, would the work they are doing actually look different? | |
| Jul 10, 2021 at 18:24 | comment | added | Samuel Muldoon | @Sarov Imagine a person putting in roofing nails. Now imagine two people performing the same roofing job; with one person working in the United States, and the other person working in former Czechoslovakia. The two workers might not use the same word for "nail", but they are doing the same thing. SCRUM is useful only if when you dump SCRUM terminology in the trash, your engineers and software developers are actually working differently after SCRUM was adopted than before you used SCRUM. | |
| Jul 10, 2021 at 18:17 | comment | added | Samuel Muldoon | @Sarov A set of business practices is only useful if those practices can be implemented without using bizarre language. Whoever is in change might decide between (1) having daily 15 minute meetings or (2) a 75 minute meeting once per week. Suppose that daily meetings are more effective than once-per-week meetings. I am not sure that is true, but that is the point. If daily meetings make the team more productive, then it won't matter if you call the meetings "SCRUMS" or not. | |
| Jul 10, 2021 at 18:12 | comment | added | Samuel Muldoon | @Sarov. There are all sorts of business practices in the world. Some companies have employees pair-up into two-person teams having one experienced software developer and one less-experienced computer programmer. I do not know if is so-called "pair programming" is effective or not. However, I do know that if pair programming is effective, it will at least as effective if described using language which employees are more comfortable with. If you can adopt SCRUM practices without abusing the English language, then use SCRUM. | |
| Jul 8, 2021 at 18:54 | comment | added | Sarov | I could be wrong, but it sounds like you're suggesting that people who use Scrum terminology are incompetent and try to make themselves appear smarter than they are? If that was not your intent, you should edit to clarify. | |
| Jul 8, 2021 at 18:51 | history | edited | Sarov | CC BY-SA 4.0 |
deleted 6 characters in body
|
| Jul 8, 2021 at 18:36 | review | First posts | |||
| Jul 8, 2021 at 18:54 | |||||
| Jul 8, 2021 at 18:32 | history | answered | Samuel Muldoon | CC BY-SA 4.0 |