i think that in those days, we were still thinking "the biz says what, dev does it". that's certainly the scrum model.
yes, we wanted collaboration, /and/ saw this still common dynamic.
i'm still not sure we were wrong. much (most?) dev is work for hire.
yes, we wanted collaboration, /and/ saw this still common dynamic.
i'm still not sure we were wrong. much (most?) dev is work for hire.
as such, there likely will be a list of "requirements" and in that very common real context, backlog is a fairly decent way to handle it.
ideally, and increasingly often, there's a better more collaborative way. but on the ground, scrum can be a decent gateway to better.
ideally, and increasingly often, there's a better more collaborative way. but on the ground, scrum can be a decent gateway to better.
what was not obvious was that scrum would be used "at arm's length", so that real collaboration would not arise.
perhaps we were too optimistic, but i'm not sure that the biz/dev split model will ever be as obsolete as we might like.
perhaps we were too optimistic, but i'm not sure that the biz/dev split model will ever be as obsolete as we might like.
