You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- 42Indeed. If the team wants to "stop doing Scrum" and feels they are "doing Kanban" anyway, why not do Kanban? I'm not necessarily saying you (Daniel Ziga) should do Kanban, but you certainly should consider it. That said, there should be specific things to do/not do in the retrospective. Nevertheless, starting the conversation with, "hey team, how should we rework our process?" may at least stimulate an interesting discussion and positions them to have interest and buy-in in whatever results from it (as long as it doesn't largely dismiss their concerns).Derek Elkins left SE– Derek Elkins left SE2017-08-15 10:00:07 +00:00Commented Aug 15, 2017 at 10:00
- 98Remember also that Scrum is not a goal; it is a means. The goal is building quality software, with a committed team. If Scrum is not accomplishing the goal, get rid of it.Erik– Erik2017-08-15 10:26:52 +00:00Commented Aug 15, 2017 at 10:26
- @DerekElkins I will definitely try out your suggestion about asking them how we should rework our process.user42401– user424012017-08-15 10:57:01 +00:00Commented Aug 15, 2017 at 10:57
- 24@Frank I hear you. Reflecting over myself and my point of view I will admit that I have been focusing too much on getting the team to work following Scrum guidelines rather than staying true to the agile manifesto. Thank you for your response.user42401– user424012017-08-15 10:59:58 +00:00Commented Aug 15, 2017 at 10:59
- 15I agree with your answer and I think this blog post by Brian Knapp fits the issue perfectly: brianknapp.me/developers-dislike-agile “In fact, Scrum done “right” according to scrum isn’t agile at all. Scrum the way it is taught is a process designed not to change. That is a massive failure. It breaks the most important principle of agile.”Michael– Michael2017-08-15 16:40:53 +00:00Commented Aug 15, 2017 at 16:40
| Show 3 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you