Timeline for Senior developers 'reject' agile. What now?
Current License: CC BY-SA 4.0
28 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 18, 2021 at 13:48 | comment | added | Flater | @workerjoe "The customer is, ultimately, the boss." No, the boss is the boss. And the boss wants to please his customers, but that does not mean that a customer can override the boss when they disagree. For example, customers might not care for certain regulations or approaches that a company does. To put it simply, if customers called all the shots, you can throw good practice development right out the window. | |
| Jul 10, 2021 at 22:08 | history | edited | Tiago Cardoso | CC BY-SA 4.0 |
Bringing clarification from comments to question
|
| Jul 10, 2021 at 9:20 | comment | added | Tiago Cardoso | It seems there's a few questions and answers being added as comments. They could add much more value to the community if raised and answered separately... otherwise we just clog the comment area with side questions (and they may be removed when not related to the actual question). | |
| Jul 9, 2021 at 12:09 | comment | added | Dpeif | Kind of a red flag that they're using "a variation of scrumban" methodology. So, a variation of a combination of two highly-fluid practices. My guess is that could be a good place to start the retrospective discussion: how did we get here, and where is "here"? | |
| Jul 9, 2021 at 7:46 | comment | added | Thorbjørn Ravn Andersen | They don't see any advantages in working the way you think they should. You might have to demonstrate why yours is a better idea. | |
| Jul 8, 2021 at 20:34 | comment | added | workerjoe | @Flater "Authority" is a tricky thing. The customer is, ultimately, the boss. If the product owner is the only person on the team who understands Agile, he can and should craft his requirements (sprint length, definition of done, information sharing requirements, etc) to guide the developers toward an agile process that can deliver them. | |
| Jul 8, 2021 at 18:32 | answer | added | Samuel Muldoon | timeline score: 1 | |
| Jul 8, 2021 at 18:07 | answer | added | Mike Robinson | timeline score: 2 | |
| S Jul 8, 2021 at 13:10 | history | suggested | Peter Mortensen | CC BY-SA 4.0 |
Copy edited (e.g. ref. <https://english.stackexchange.com/questions/4645/is-it-ever-correct-to-have-a-space-before-a-question-or-exclamation-mark#comment206109_4645>). Added some information from comments.
|
| Jul 8, 2021 at 11:17 | comment | added | Flater | @workerjoe: Yes and no. The customer's demands are a strong incentive, but they are not equivalent to having the authority to dictate the dev process. If the developers are able to meet customer expectations using whatever dev process, then that's fine. If you are tailoring your customer expectations specifically to manipulate them into agile being the only possible way, for no reason other than to make them do agile, then you're overreaching as a PO. | |
| Jul 8, 2021 at 11:17 | answer | added | Carl Witthoft | timeline score: 1 | |
| Jul 8, 2021 at 9:03 | review | Suggested edits | |||
| S Jul 8, 2021 at 13:10 | |||||
| Jul 7, 2021 at 8:25 | answer | added | AnoE | timeline score: 2 | |
| Jul 7, 2021 at 8:04 | comment | added | Bogdan | @allad: in a Scrum team developers are responsible for the technical perspective, the PO for the business, and the SM for the process aspect. It's a collaboration of these three things and there are overlaps, but at the end of the day the SM is accountable for the Scrum implementation. It also matters what kind of SM you have. You say the company does Scrumban. It remains to be seen how much of it is Scrum + Kanban and how much is something else. From your post, there will possibly be "something else". | |
| Jul 7, 2021 at 7:48 | answer | added | Barnaby Golden | timeline score: 13 | |
| Jul 7, 2021 at 6:40 | comment | added | allad | Thank you all for your feedback. To add context, I don't think the company has a scrum master, I'll discover soon enough ho's in charge of keeping the rituals on track. Is not having a scrum master necessarily a problem ? | |
| Jul 6, 2021 at 21:33 | comment | added | Josh Part | @workerjoe I'm not "dismissing" his concerns, I'm just saying he should double-check what his role really is (or what his role his recruiter expects to be). If the recruiter/project managers/bosses are the ones trying to make the POs tell the engineers/devs how to do their job, that might be where the real problem is. I agree with you: his job as a PO should be define requeriments and expect increments per the delivery schedule; what he shouldn't do is tell the devs what PM tool should they use, how long their sprints should be, etc. | |
| Jul 6, 2021 at 19:12 | comment | added | Bogdan | @allad: If you go in thinking things are broken, you will have a tendency to also go in with some solutions to fix them. But realistically speaking, you didn't form your own opinion on the matter. You were provided with the opinion of your recruiter. That opinion might be accurate or it might not. You should wait until you start work to see what the situation really is. Then take it from there. And as others have mentioned, as a PO, whatever this is, isn't for you to fix. The SM has a great responsibility as well as everyone else. | |
| Jul 6, 2021 at 18:58 | comment | added | workerjoe | @JoshPart I wouldn't be so quick to dismiss the OP's issues. As product owner, he is the "customer", and he certainly has input on what should be delivered and when. He can set expectations that product increments be delivered at specific intervals and that the team participate in sprint review and sprint planning meetings. If they cannot deliver, because their processes do not allow them to deliver finished software in regular increments, he can put the onus on them to adopt those methods. | |
| Jul 6, 2021 at 17:44 | comment | added | Josh Part | Not an expert on the topic, but I see a few things that don't add up. As a Product Owner, you don't have (and shouldn't have) ANY repercussion over the dev process, so if one of your challenges is to "renew processes", those should be operative, not engineering ones. If they are using some form of scrum, and the devs are recluctant to follow such framework, then that's the scrum master's responsibility, not yours | |
| Jul 6, 2021 at 16:27 | answer | added | fishinear | timeline score: 7 | |
| Jul 6, 2021 at 15:21 | history | became hot network question | |||
| Jul 6, 2021 at 15:00 | history | tweeted | twitter.com/StackProjects/status/1412426150006112260 | ||
| Jul 6, 2021 at 13:34 | answer | added | Niels van Reijmersdal | timeline score: 3 | |
| Jul 6, 2021 at 11:39 | answer | added | nvogel | timeline score: 5 | |
| Jul 6, 2021 at 11:19 | answer | added | Thomas Owens♦ | timeline score: 33 | |
| Jul 6, 2021 at 8:55 | history | edited | allad | CC BY-SA 4.0 |
edited title
|
| Jul 6, 2021 at 7:18 | history | asked | allad | CC BY-SA 4.0 |