Hi,
we just had an interesting release retrospective, most people feel that
Scrum works well for us, albeit in a modified form. (Estimating in hours
rather than story points, specialist developer only teams rather than cross
functional teams,
bug fixes must count towards velocity as that is the majority of our work,
user stories are more like technical descriptions of what needs to be done,
rather than the user-centered "as a, i want, so that" format.)
However people have noticed some issues, relating to basically all aspects
of our development process, such as flexibility, role of the PO (as our
support consultants and project managers have the customer contact), less
communication within the department now that we are split up into small
teams etc, lots of little things.
We are happy overall, but have a feeling that it may not fit quite right.
A lot of what I read suggests Scrum evolved in an environment of project
based, single customer, internal development of new projects, rather than
the Product based, multiple customer, maintenance work that we are involved
in.
We will be evaluating things next week, and I wondered if anyone had any
pointers to adjustments to the standard scrum that could make it more ideal
for teams like ours.
Hi, we just had an interesting release retrospective, most people feel that Scrum works well for us, albeit in a modified form. (Estimating in hours rather...
Hi Kurt. A couple of suggestions. 1. You could treat bugs as scrum traditionally treats stories. That is, add them to the backlog, and have someone prioritize...
... That is pretty much what we do now. ... We used to have timeboxes within our sprints for bug-fixing and new development. Now each team takes turns being...
Lately I'm hearing "kanban" tossed around in the software process world with almost mystical significance. I'm not sure it's properly understood that in the...
Michael, How much time have you invested in discovering the current practices of those applying Kanban to software engineering before deciding that it is not...
I guess that was a bit of an outburst, let me offer some context. I believe that this group is a valuable resource for all readers from novice to experienced...
Hello, ddraperuk. On Thursday, July 9, 2009, at 3:08:39 PM, you ... One of these things is not like the other. I'm really wondering why you have taken such...
As long as people are posting messages on ScrumDevelopment about "kanban principles" such as limiting the size of the backlog, Scrum developers need to be able...
... I am no expert, but it seems as if kanban has in fact gained a bit of significance in the software world since it first appeared in the TPS many years ago....
... It's a distinction being drawn by some in the community, but it's hard to distinguish by ear, and it's a barrier for people who know something about...
... Yes, case sensitivity in spoken language can be more than a little subtle :^) But at least in written form the distinction exists as a cue, one that can...
Ooh. Quoting seems to be working again :) ... I'm trying to get into the habit of talking about "Kanban Systems" as opposed to kanban or Kanban. I still fail...
Yes, odd. I have encountered many "Scrum versus Kanban" discussions, blog posts and conference submissions. It seems a little like saying "which is better, the...
Hi Tobias, ... I disagree with this and I don't think its helpful. My reaction is probably the same as yours would be if I said "Scrum is a tool, Kanban is a...
Hi Karl, I read the article. Good stuff. Honestly, if you changed every occurrence of the word "Kanban" for "Scrum" your article would still read intelligently...
Tobias: I read the article. Good stuff. Honestly, if you changed every occurrence of the word "Kanban" for "Scrum" your article would still read intelligently...
You can't be doing scrum without Sprints. However, you don't have to do batch planning, it can be incremental. The sprint is mainly there as a big feedback...
... Right. The ideas are not mutually exclusive. Kanban simply gives a different way of establishing a cadence to achieve the feedback loop which some teams...
Yeah, I think it's useful, too. There cadence to the WIP (the planning cadence) is very useful to have separate from the review (with stakeholders) cadence Dan...
... add that is not already in Scrum? ... limit work in progress, as opposed to using a time-box to limit work in progress. Actually the time box does not...
... As far as I know, these are really good ideas but not inherent to Scrum? Ron Jeffries www.XProgramming.com www.xprogramming.com/blog There is no award for...
No. Not inherent to scrum. Scrum is much too general a tool for that. Scrum merely helps you do the things you value better. I recommend that you value these...
Interesting point. But common sense has to relate to some value system. Value systems are not absolute. Some companies value high quality product, some value...
Hi, ... I think this characterizes one of the challenges with Scrum. Scrum is said to be this and that, all of which complicate the understanding of what Scrum...