Kanban is not a paradigm in and of itself, but a way to manage projects, tasks and team planning. Projects are done just in time, on a rolling basis.
I'm going to repeat the very last paragraph in this article because it is so important and so clear - "Constant communication, assessment, and reorganization is necessary to complete high quality software projects. Increasing transparency, visibility, and cooperation among team members is the best way to facilitate software development."
I really think we should all print that section out in a large font and put it up where we work in order to make sure we remember it and try to stick to it.
No comments:
Post a Comment
Note: only a member of this blog may post a comment.