The next question comes is – how does one set the Due Date? It’s used as a simple guideline to the team member to complete a card/ task can be useful. One is not talking about going back to the old ways – wherein the Due Date becomes a deadline cast in stone and quality/ technical debt become a secondary consideration. So, in many situations, use of a Due Date at the card or task level becomes useful. For projects that work on fixed budgets, such slippage can soon pile up and cause management escalation. 5 days of work can easily stretch to 7 days when no expectation is set with the developer of a 5-day deadline. While project teams are expected to be self-organizing and self-driven, the reality might be quite different and the absence of Due Dates can cause loss of momentum within the team. The question is: should teams that are used to Due Dates, consider using them on the cards/work items on their Kanban board? In contrast to Scrum, Kanban systems, being flow centric, take away the pressure of the Sprint date. If something needs to be done by an intermediate milestone (like a customer demo date), Due Date can focus the participating team members to that milestone. In spite of the issues mentioned earlier, Due dates can help team members working on different user stories belonging to the same MMF align their completion date. So, the Sprint end date serves as a reasonable reminder to the team that they need to complete their work by then.
Yes, some requirements may spill over to the next sprint but that is generally a small % of the overall Sprint scope. Someone has gone through the process of mapping the Sprint capacity with the story points that is planned in that Sprint. The team has a clear expectation that the planned scope of the Sprint needs to be completed by the end date of the Sprint. That said, Agile methodologies, specifically Scrum, inherently have a Due Date. The net effect is that work quality is compromised and technical debt piles up. Quite often, that translates into short cuts in Design/ Testing activities. Focus on Due Dates results in teams working under significant pressure. Agile thinking has discouraged the use of Due Dates. Many teams adopting Kanban come from Agile background. Kanban 101 Comprehensive Guide to Kanban.PM/ Work Management 101 Comprehensive Guide to PM.Success Stories What our Customers say about us.Customer Support Digité Products Support.
Youtrack kanban professional#
Professional Services Application Integration Services.Training & Consulting Consulting Services from Digité.Insurance Products New Product & Market Initiatives.Global Delivery Management Enabling the Global Technology Business.Managed Services Comprehensive Managed Services Platform.Hybrid Agile Project Management Bridging the Traditional and the Agile.Quality Management Building Quality Products & Applications.Agile Marketing Data Driven, Iterative and Responsive.DevOps Solutions Continuous Delivery & Deployment.AI & Machine Learning Automate your Enterprise.
0 kommentar(er)
