We recently moved away from a pure scrum delivery within our team, but chose to retain some of the best practice elements of scrum - one of which was user stories.
We create user stories to capture the user requirement and the outcome of the activity, but manage our work via a kanban or 'Kanplan' board.
This has worked well within my team, so no real negative for us. However this is because we wanted to move away from running timeboxed sprints which you obviously get with scrum quite neatly, if this is a requirement for your team you may run into issues, if not, then there is no reason why technically you can't use user stories with kanban.
Hi @Daniel Smith ,
Thanks, this is really helpful.
I suppose the only impact will then be on the reporting metrics you can get out of this kind of setup?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's right - we're not relying too heavily on reporting, as we're a small co-located team so we have good visibility of activities anyway.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.