Dynamic Priority Setting

𝗛𝗼𝘄 𝗜 𝗼𝗽𝘁𝗶𝗺𝗶𝘇𝗲𝗱 𝘀𝗽𝗿𝗶𝗻𝘁 𝗽𝗹𝗮𝗻𝗻𝗶𝗻𝗴 𝘂𝘀𝗶𝗻𝗴 𝘁𝗵𝗲 𝗞𝗻𝗮𝗽𝘀𝗮𝗰𝗸 𝗣𝗿𝗼𝗯𝗹𝗲𝗺 📦 What do factories and software development have in common? I decided to take a concept I’d used in manufacturing and apply it to sprint planning. Well, let’s just say it worked out better than I expected… 𝗧𝗛𝗘 𝗖𝗛𝗔𝗟𝗟𝗘𝗡𝗚𝗘 🎯 In Scrum, you break a project into smaller chunks called sprints, which are time-boxed, typically 2-4 weeks long. Each sprint has a list of tasks from the product backlog, each with an estimated development time and priority set by the product owner 📋.  The goal is to figure out which tasks to take on in the sprint, given the fixed time, to maximize value. This is essentially a knapsack problem, where the sprint is the knapsack with limited capacity (in this case, the number of available days), and the backlog tasks are the items, with their time estimates as weights and their priorities as values ⚖️. 𝗧𝗛𝗘 𝗦𝗢𝗟𝗨𝗧𝗜𝗢𝗡 💡 To solve this, I modeled the problem using dynamic programming. Here’s how it works: 1. Break down the tasks: each task has a time to complete and a priority. 2. Set constraints: the total time available for the sprint (let’s say 10 days) is the capacity of the “knapsack.” 3. Calculate values: I used dynamic programming to decide which tasks provide the highest value without exceeding the available time ⏱️ For example, let’s say we have six tasks with the following times and priorities: Task Time (days) Priority 1     10        6 2     6         5 3.    6         4 4     4         3 5     3         2 6     2         1 The goal is to select the tasks that maximize value without exceeding the 10-day limit 🏁 𝗧𝗛𝗘 𝗢𝗨𝗧𝗖𝗢𝗠𝗘 🎉 Through dynamic programming, I calculated the optimal combination of tasks that fit within the 10-day sprint. The most valuable tasks to prioritize were tasks 2 and 4. This allowed the team to focus on high-priority work right at the start of the project, optimizing the sprint without overloading the team 💪 It was a fun experiment to see how problem-solving techniques used in other industries can be applied in software development. And it’s a great reminder that optimization isn’t just about finding the best solution — it’s about making the process more efficient and getting the most value out of the resources at hand 🔧

Not all shipments are created equal. Some deliveries are urgent, with customers counting the minutes until they arrive (... me with Amazon deliveries). Others have more flexibility. So, how do you decide what gets priority? Well, the final piece of the route planning and optimization puzzle this week are customer requirements and prioritization. It's about balancing what's urgent with what's efficient, ensuring that every shipment gets where it needs to be, exactly when it needs to be there. But here's the catch: prioritization doesn't work in isolation. It only works when paired with data-driven decision-making, dynamic routing, and optimized loads & vehicle utilization. Here's how it all connects: 📦 Customer requirements are the starting point. By understanding delivery windows and shipment urgency, planners can categorize shipments into priorities. Critical shipments can then be routed through the most time efficient paths while less-urgent shipments can balance time and cost. 📦 Data-driven decision making backs these priorities by insights. Real-time data helps planners adapt to disruptions that can impact high priority shipments, while historical data informs strategies to prevent delays in the first place. 📦 Dynamic routing allows flexibility when things don't go as planned. Need to reroute a time-sensitive shipment? No problem! Dynamic plans help keep high-priority deliveries on track without throwing hte rest of the schedule into chaos. 📦 Load optimization & vehicle utilization make sure that every truck is working efficiently, even when prioritization shifts the focus to critical shipments. Grouping similar loads and assigning the right vehicles create the flexibility to adjust without wasting resources. By aligning customer needs with operational strategies, companies can do more than just meet delivery windows. At its core, prioritization is about creating value by aligning customer needs with broader supply chain goals. Think about how meeting delivery windows impacts production, warehousing, inventory, other shipments... Every shipment is another step toward an interconnected, responsive, and resilient supply chain. #supplychain #logistics #transportation #routeplanning

🔍 ServiceNow Case #Study: #Automating Impact, Urgency, and Priority Fields Using #Data #Lookup #Definitions — No #Code Involved! Today, I worked on an #insightful #ServiceNow use case that aimed to #automatically populate the fields Impact, Urgency, and Priority based on the selected values of Sub-category and #Component — and I achieved this without writing a #single line of code! 🎯 Objective: To #dynamically set the Impact and Urgency fields based on predefined combinations of Sub-category and #Component, and derive the Priority field based on the resulting Impact and Urgency — all using native platform #capabilities. To implement this, I leveraged #Data Lookup #Definitions — a powerful yet #underutilized no-code feature in ServiceNow. 📘 What are Data Lookup Definitions? #Data Lookup Definitions in ServiceNow allow you to automatically populate or modify field values based on #conditions, ensuring consistency and reducing manual intervention. A typical Data Lookup rule: #Matches certain input field values (e.g., Sub-category = Software, Component = Email) #Searches a #matcher table for a corresponding rule Automatically sets #target fields (e.g., Impact, Urgency, Priority) based on the rule ⚙️ Step-by-Step Implementation: ✅ Step 1: Created a custom table named "#Business #Support", and designed the ticket form using Form #Builder, Form #Design, and Form #Layout. ✅ Step 2: Created another custom table called "#BS #Priority #Lookup", extending it from the Data Lookup #Matcher #Rules table (sys_data_lookup_rule). 🔎 This table holds all the #logic to #evaluate conditions and apply field values based on #matches. ✅ Step 3: On the #BS #Priority #Lookup table, I configured #form fields to capture the Sub-category, Component, Impact, Urgency, and Priority #mappings. ✅ Step 4: Navigated to the Data Lookup #Definitions module and created a new #definition. ✅ Step 5: Set the following: #Source Table: Business Support #Matcher Table: BS Priority Lookup #Matcher Fields: Sub-category & Component #Setter Fields: Impact, Urgency & Priority 🔁 How It All Comes Together: When a user submits a form in the #Business #Support table: The platform checks for matching rules in the #BS #Priority #Lookup table If an exact match is found on Sub-category and Component, it auto-sets the Impact, Urgency, and Priority fields — streamlining #triage without custom #scripting! 💡 This approach not only #promotes #scalability and #consistency but also reduces maintenance overhead by avoiding #scripted #logic. If you're exploring ways to deliver #smarter #workflows in #ServiceNow without code, I highly recommend #experimenting with #Data #Lookup #Definitions. #ServiceNow #NoCode #Automation #WorkflowDesign #PlatformConfiguration #ServiceManagement #ProcessImprovement #DataLookup #ImpactUrgencyPriority #LinkedInLearning

A high-octane business environment with double-digit growth objectives presents a challenge of handling the "problem of plenty." Strategic prioritization, focus, and discipline are crucial in navigating this scenario effectively. Prioritization Frameworks: 1.Eisenhower Matrix to categorize initiatives based on urgency and importance. 2.MoSCoW Method to label initiatives as Must-Haves, Should-Haves, Could-Haves, and Won't-Haves. 3.Kano Model to classify initiatives based on customer delight, meeting expectations, or fulfilling basic needs. Focus on High-Impact Initiatives: 1. Identify Key Performance Indicators (KPIs) to concentrate on initiatives with significant impact. 2. Conduct Cost-Benefit Analysis to evaluate ROI and resource requirements. 3. Ensure strategic alignment by assessing initiatives against the organization's goals. Resource Allocation and Optimization: 1. Align resource allocation with initiative priorities through Resource Capacity Planning. 2. Manage initiatives as a portfolio with Portfolio Management for effective resource utilization. 3. Implement Agile Methodologies for flexibility and rapid response to changing priorities. Governance and Decision-Making: 1. Define clear decision-making criteria for evaluating and prioritizing initiatives. 2. Establish a governance structure to ensure strategic alignment and resource allocation. 3. Regularly review progress, adjust priorities, and reallocate resources as needed. Cultural and Behavioral Aspects: 1. Foster a culture that values prioritization, focus, and discipline. 2. Encourage open communication for understanding and alignment of priorities. 3. Recognize and reward effective prioritization and focus among employees. By incorporating these strategies, businesses can effectively address the challenges posed by a dynamic business environment, driving growth while maintaining focus and discipline. #DProblemofPlenty Manjushree Technopack Limited (MTL) Gladys Caligagan