Kanban in a Multi-project Changing Team
This presentation focuses on improvements made over two years of using Kanban and tries to share some ideas for further work with Kanban.
Project Management for Software Development
Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
This presentation focuses on improvements made over two years of using Kanban and tries to share some ideas for further work with Kanban.
Have you ever worked in a software development super team? The kind of team where the process is the natural flow of the team. Everyone on the team working on his or her parts of the project and it all comes together as one perfect whole. Discussions flow easily, decisions...
In real world agile teams, traditionally defined rigid roles are rapidly being displaced by a culture of collective ownership of the product. Responsibilities are being decoupled from specialties by a collection of operators with overlapping skills, and chief among them is technical acumen.
Collaboration is an essential ingredient in healthy Agile project communities, yet in my experience truly effective collaboration is perhaps the hardest thing to do well. We have become so adept at using e-mail, instant messaging, voice mail, and telephones to communicate that we have lost our preference for face-to-face communications.
We spend a large portion of our time thinking about code and technical project issues. What about the people side of things? The majority of project failures occur because of people, not technology. What we need are guides that help us navigate the waters between the people around us.
One very important property in Kanban is called “make process policies explicit”. This includes well-defined interfaces to upstream as well as downstream partners. Kanban tries to define these interfaces on a very abstract level, because Kanban is a change management approach that wants to integrate with several possible project management...
Not everyone is a fan of the self directed self organizing team. It flies in the face of traditional project management, and often conflicts with the traditional organization model. The benefits of self directed teams however are too big to ignore and now we have scientific proof as to why.
Inspired by the Gang of Four patterns for object oriented software development, Michael Duell proposes in this article some patterns for dysfunctional project management behavior. He classifies them in the cremational, destructural and misbehavioral patterns categories.