Waterfall Project Management Approach

How to Extract Information from Stakeholders 🎯 Getting accurate information from stakeholders can make or break your financial planning process. Each stakeholder speaks a completely different language and focuses on totally different metrics. The secret? Knowing exactly what to ask and how to ask it. ➡️ CEO CONVERSATIONS CEOs think big picture, so focus on strategic direction and vision. You want company strategies for next quarter, budget allocation expectations, risk tolerance levels, and market positioning goals. The money question: "What are the top 3 strategic priorities that should drive our Q4 planning?" ➡️ HEAD OF SALES Sales leaders live and breathe pipeline projections and customer acquisition costs. Get those sales pipeline projections, customer acquisition costs, territory performance data, and resource requirements for targets. My go-to approach: "What's the realistic revenue projection for Q4, and what support do you need?" ➡️ MARKETING DIRECTOR Marketing lives for lead generation and brand metrics. You need campaign performance metrics, lead generation forecasts, brand awareness initiatives, and marketing budget requirements. Hit them with: "How many qualified leads can marketing deliver to support the sales targets?" ➡️ HR MANAGER HR thinks talent and workforce planning 24/7. Grab headcount projections, recruitment timelines, employee retention rates, and training and development needs. Start here: "What's our hiring timeline to support the growth plan, and any retention concerns?" ➡️ ENGINEERING LEAD Engineering leaders obsess over product development roadmaps. Collect that product development roadmap, technical debt priorities, infrastructure requirements, and team capacity information. The must-ask question: "What features can be delivered by Q4, and what technical investments are critical?" ➡️ ACCOUNTING MANAGER Accounting thinks financial health and compliance every single day. Get cash flow projections, budget variance analysis, financial compliance requirements, and cost optimization opportunities. The essential question: "What's our cash flow outlook, and are there any financial constraints for our growth plans?" ➡️ UNIVERSAL BEST PRACTICES These six practices work with EVERY stakeholder: Be Specific: Ask for concrete numbers, dates, and measurable outcomes rather than vague commitments. Respect Their Time: Come prepared with focused questions and provide context upfront. Speak Their Language: Use terminology and metrics relevant to their department and priorities. Validate Understanding: Repeat back key points to ensure alignment and avoid miscommunication. Follow Up: Send summaries of key decisions and next steps within 24 hours. Close the Loop: Show how their input directly influences decisions and outcomes. === What's your approach to stakeholder communication? Share your best practices in the comments below 👇

Not All Maintenance is Created Equal In many organizations, maintenance is still misunderstood as simply fixing equipment when it fails. But in high-performing operations, maintenance is not a reaction, it is a carefully designed strategy for reliability, cost control, and asset longevity. The Maintenance Body of Knowledge (BoK) provides world-class benchmarks for how work should ideally be distributed: 1 Unplanned (Breakdown) Maintenance (<10%) The most disruptive and expensive form. Breakdowns cost 3-5 times more than planned work when you factor in downtime, safety risks, and lost production. In leading organizations, breakdown work is the exception, not the rule. 2 Planned Maintenance Preventive (Time-Based/Calendar-Based) (30-40%) Scheduled inspections, servicing, and part replacements. Necessary to address wear-and-tear, but if overdone, it risks wasting resources. Corrective Maintenance (10-15%) Work identified during inspections or condition checks that needs intervention before failure occurs. This is where structured planning and backlog management keep plants stable. Predictive / Condition-Based (40-50%) The most advanced form of planned maintenance. Uses sensors, data analytics, and condition monitoring to act just before a failure develops. Extends asset life while optimizing costs, making it the gold standard for reliability. World-class organizations manage their portfolios to steadily reduce unplanned maintenance while shifting investment toward predictive strategies. This doesn't happen overnight, it requires leadership, systems, and a culture of reliability. Maintenance leaders don't just keep the lights on. They shape business outcomes by deciding where each maintenance hour and rand/dollar should go. Every percentage point shift away from unplanned work translates into: Lower costs Higher safety and reliability More predictable operations #Reliability Leadership #Maintenance Excellence #Predictive Maintenance #AssetManagement #OperationalExcellence Image credit: ResearchGate

Why-Why Analysis: (Example: Machine Breakdown) Problem Statement: The hydraulic pressing machine's malfunction disrupted the assembly line 1.  Why: The machine stopped because the motor wasn’t running. 2.  Why: The motor stopped because it overheated and triggered a safety shut-off. 3. Why: It overheated due to not enough lubrication. 4. Why: The lubrication system failed because the oil pump wasn’t working properly 5. Why: The pump failed because its filter was clogged and wasn’t cleaned regularly Root Causes: The pump failed because its filter was clogged and wasn’t cleaned regularly Evidence/Data/Fact: 1. Machine logs show temperature spikes before the failure. 2. Maintenance records indicate the oil filter was overdue for replacement. 3. Inspection found a clogged filter and insufficient lubrication. Solution Idea 1. Maintenance Schedule: Set up regular checks and replacements for oil filters. 2. System Upgrade: Invest in a better oil pump and filter system. 3. Monitoring: Add temperature sensors to catch overheating early. Corrective Action 1. Schedule Implementation: Create and follow a maintenance calendar for oil filter replacements. 2. Training: Train maintenance staff on proper lubrication care and importance of timely replacements. 3. System Upgrade: Buy and install higher-quality oil pumps and filters. 4. Sensor Installation: Install temperature sensors to alert of potential overheating issues. Preventive Measures 1. Documentation: Use a maintenance checklist and ensure it’s followed. 2. Audits: Conduct regular checks to make sure maintenance schedules are being followed. 3. Supplier Review: Choose reliable suppliers for oil pumps and filters.

I've spent over 4,000 hours in stakeholder requirement-gathering meetings! Save hours of your life by asking these questions: 1. What do they plan to use the data for? 1. What initiative are they working on? 2. How will this initiative impact the business? 3. Is this for reporting or optimizing existing workflows? Understanding the purpose of the data helps you define its impact. 2. How do they plan to use the data? Will they access it via SQL, BI tools, APIs, or another method? 1. Do they have a workflow to pull data from your dataset? 2. Do they just do a `SELECT *` from your dataset? 3. Do they perform further computations on your dataset? This determines the schema, partitions, and data accessibility needs. 3. Is this data already present in another report/UI? 1. Is this data already available in another location? 2. Do they have parts of this data (e.g., a few required columns) elsewhere? Ensuring you're not recreating work saves time and avoids redundancy. 4. How frequently do they need this data? 1. How frequently does the data actually need to be refreshed? 2. Can it be monthly, weekly, daily, or hourly? 3. Is the upstream data changing fast enough to justify the required latency? Understanding frequency helps you determine the pipeline schedule. 5. What are the key metrics they monitor in this dataset? 1. Define variance checks for these metrics. 2. Do these metrics need to be 100% accurate (e.g., revenue) or directionally correct (e.g., impressions)? 3. How do these metrics tie into company-level KPIs? Memorize average values for these metrics; they’re invaluable during debugging and discussions. 6. What will each row in the dataset represent? 1. What should each row represent in the dataset? 2. Ensure one consistent grain per dataset, as applicable. 7. How much historical data will they need? 1. Does the stakeholder need data for the last few years? 2. Is the historical data available somewhere? Ask these questions upfront, and you'll save countless hours while delivering exactly what stakeholders need. - Like this post? Let me know your thoughts in the comments, and follow me for more actionable insights on data engineering and system design. #data #dataengineering #datastakeholder

How do you gather requirements... when there's literally nothing to start with? (Brand new project in the Discovery / Inception Phase) If you’ve ever been handed a brand-new project and thought: “Where do I even start with requirements?” ...you’re not alone. When there’s no existing system, no previous project to reference, and stakeholders aren’t quite sure what they need yet — it can feel like you're building the plane while flying it. Here’s the approach I use as a Business Analyst when I’m brought in at square one: → Understand the business context. What are we trying to solve? Why now? → Map out key stakeholders. And don’t just talk to the usual suspects — bring in Legal, Compliance, Security, etc., early. Cross-functional input saves you rework later. → Break the project into logical categories. Whatever the project is delivering, try to break it down into high-level process steps. This will help when workshopping requirements with stakeholders, so they can focus on different requirements. → Capture high-level needs. And yep - I use user stories here too. Even at this early stage. It keeps things outcome-focused. → Document just enough. I don’t write 50-page BRDs anymore. I use Confluence tables, Jira, and lightweight templates that the whole team can engage with. → The goal at this stage? Clarity, alignment, and momentum... not perfection. Because let’s be honest: the first version of your requirements will evolve. And that’s a good thing. 💡 Want to become the kind of BA who can confidently lead from day one of a project? Learn how to: ✅ Guide discussions when the path isn’t clear ✅ Keep documentation lean but effective ✅ Become the go-to for “what are we actually trying to do here?” Question for you...How do you approach requirements for a brand new project? Do you use a BRD, Confluence, sticky notes… or something else? If you found this helpful, give me a follow Matthew Thomas I share regular micro-lessons to help you level up your BA career. #BusinessAnalysis #RequirementsGathering #NewProjects #BusinessAnalystLife #AgileBA #LeanDocumentation #UserStories #Confluence #Jira

𝐖𝐡𝐚𝐭 𝐲𝐨𝐮 𝐬𝐡𝐨𝐮𝐥𝐝 𝐤𝐧𝐨𝐰 𝐛𝐞𝐟𝐨𝐫𝐞 𝐛𝐞𝐜𝐨𝐦𝐢𝐧𝐠 𝐚 𝐁𝐔𝐒𝐈𝐍𝐄𝐒𝐒 𝐀𝐍𝐀𝐋𝐘𝐒𝐓 Being a relatively new business analyst, I am coming to a realization that sometimes, it is less about  the amount of knowledge of tools and templates, and more about avoiding the traps that quietly ruin good projects. I identified some, and thought to share: 1. Skipping the BRD and jumping straight into the FRD You get excited and write a detailed FRD before anyone has even agreed on the actual business problem and you beautifully document solution to the wrong problem. Instead, start with the business why: goals, pain points, success metrics. Then move into how the system should work. 2. Treating all stakeholders the same You send updates to everyone, and long reports to people who’ll never read them. Meanwhile, the one person who can block the entire project feels unheard. Apply stakeholder mapping instead (refer to my previous post) 3. Going too deep, too early When you document every edge case on day one, or an 100-page FRD before the idea is even approved. You could start high-level, get alignment. Then iterate. Requirements gathering is a conversation, not a one-time brain dump. 4. Not validating requirements Writing everything all by yourself, then “handing it over” and moving on. It does not work like that, you have toL; ✅ Walk stakeholders through your understanding. ✅ Use wireframes, mockups, or simple flows. ✅ Get explicit sign-off before build.  5. Weak or missing documentation “I’ll explain it on the call” does not cut it because people forget, roles change, or new devs join. Please, try to document clearly. All of the BRD, FRD, use cases, flows, acceptance criteria for easy sharing with an assumption someone will read it without you in the room. 6. Asking “What do you want?” instead of “What problem are we solving?” You deliver exactly what they asked for, and nobody uses it. You have to keep asking “Why?” until you hit the real business problem. Then design the solution around that. 7. Ignoring constraints Some go ahead to gather so many requirements like time, budget, and tech limits don’t exist. Important to ask early if there is a budget, a timeline, or even regulatory constraints. 8. Using only one elicitation technique As a BA, you cannot stick to only interviews, workshops or surveys for elicitation. Mix methods from interviews, observation, workshops, to data analysis, prototyping. Different angles will give you a better picture. Most new BA mistakes come from rushing, assuming, and not communicating enough. The BAs who grow fastest are the ones who: ✔️ Take time to understand the problem ✔️Involve the right people ✔️Write clearly ✔️Validate often ✔️Ask “why?” and “what if?” ✔️Are humble, and can say boldly, “I’m not sure, let’s clarify.” 𝑰 𝒕𝒉𝒊𝒏𝒌 𝒕𝒉𝒆𝒔𝒆 𝒄𝒐𝒗𝒆𝒓 𝒕𝒉𝒆 𝒎𝒊𝒔𝒕𝒂𝒌𝒆𝒔 𝑩𝑨𝒔 𝒂𝒓𝒆 𝒎𝒐𝒔𝒕 𝒍𝒊𝒂𝒃𝒍𝒆 𝒕𝒐. 𝑫𝒐 𝒚𝒐𝒖 𝒕𝒉𝒊𝒏𝒌 𝑰 𝒂𝒎 𝒔𝒑𝒐𝒕 𝒐𝒏?

🔥 MECHANICAL MAINTENANCE DEPARTMENT CHECKLIST (Shift | Daily | Weekly | Monthly | Yearly) Maintenance isn’t a repair activity — it’s a reliability discipline. This checklist defines clear ownership, frequency, and actions across the Mechanical Maintenance function. 🟦 SHIFT – Technician / Operator • Machine condition monitoring (noise, vibration, temperature) • Lubrication checks & top-up as per schedule • Leak inspection (air, oil, water, hydraulic) • Tightening of critical fasteners (nuts, bolts, couplings) • Abnormality tagging & immediate escalation • Basic cleaning (dust, debris, cooling fins) • Safety checks (guards, interlocks, emergency stops) 🎯 Focus: Early detection & failure prevention 🟩 DAILY – Supervisor / Engineer • Breakdown review & quick response coordination • Equipment health check (critical machines) • PM task verification & closure tracking • Spare parts consumption monitoring • Root cause analysis (5-Why for repeated issues) • Utility system check (compressors, chillers, pumps) • Work permit & safety compliance audit 🎯 Focus: Stability & quick restoration 🟨 WEEKLY – Maintenance Manager • Preventive Maintenance (PM) schedule compliance review • Predictive Maintenance (PdM) data review (vibration, thermography) • Lubrication audit & oil condition check • Alignment & balancing checks (critical equipment) • Spare inventory audit (min-max levels) • Breakdown trend analysis • Maintenance planning & backlog review 🎯 Focus: Reliability & risk control 🟧 MONTHLY – Management / Leadership • KPI review (MTBF, MTTR, breakdown %, downtime) • Critical equipment performance analysis • Cost review (maintenance cost, spare usage) • Major shutdown planning & execution review • Calibration of critical instruments • CAPA effectiveness review • Kaizen / Continuous Improvement initiatives 🎯 Focus: Performance & optimization 🟥 YEARLY – Strategic • Annual maintenance strategy & budget planning • Major overhauls & shutdown execution • Asset lifecycle assessment & replacement planning • Reliability improvement projects (RCM, FMEA) • Vendor & AMC performance review • Skill development & technical training plan • Safety audit & compliance review 🎯 Focus: Sustainability & long-term reliability 💡 Key Takeaway A strong Maintenance Department doesn’t just fix machines — it prevents failures, improves reliability, and sustains performance. Clear ownership + disciplined execution + data-driven maintenance = maximum uptime. 📌 Save | Share | Use this as your Maintenance Excellence Framework #Maintenance #MechanicalMaintenance #Reliability #PreventiveMaintenance #PredictiveMaintenance #MTBF #MTTR #RCM #FMEA #OperationalExcellence #Manufacturing #MaintenanceEngineering

📌 Dashboard Requirements Gathering 101 (How to Drive Real Decisions & Adoption) The success of a Data or BI project doesn’t start with the tool you pick or the stack you deploy. It starts earlier. It starts with something less exciting, but far more important: gathering clear business requirements. And yet, this is the step that gets skipped the most. Everyone wants to talk about architecture, pipelines, medallion layers, AI copilots… But if you don’t know what the business actually needs, none of that matters. So what does "gathering requirements" actually look like? It means sitting down with stakeholders and asking questions that sound simple on the surface, but change everything: ⤷ What decisions are you struggling to make today? ⤷ Where does data slow you down or create confusion? ⤷ Which KPIs, if you had them right now, would change how you run the business? These conversations are rarely neat. You’ll hear conflicting priorities, vague goals, and sometimes even silence. That’s normal. The job is to cut through the noise and translate it into something concrete. When you do that, everything else falls into place: 1) Data engineers know exactly which sources to prioritize. 2) Data Analysts stop debating vanity metrics and focus on useful KPIs. 3) Leaders understand what to expect once dashboards go live. And here’s what often gets overlooked: requirement gathering isn’t just about listing KPIs. It’s here to map business decisions to data, spot workflow bottlenecks, align with strategy, and create a shared language across business and technical teams. It’s where you discover that the sales team and the finance team define "revenue" differently. It’s where you realize that a monthly report isn’t enough, and what the business really needs is daily visibility. It’s where you uncover that the pain point isn’t the dashboard at all, but the manual process feeding it. Data platforms and BI tools will keep changing. Snowflake, Databricks, Fabric, Big Query, etc. They’ll evolve and new ones will appear. But the discipline of requirement gathering won’t. It’s the constant that ties technology back to outcomes. So if you’re about to start a new BI project, spend more time here than you think you need. It will save you months of rework later and it’s the best way to make sure your dashboards actually drive decisions. #BusinessIntelligence #DataStrategy

Let's understand how as a Business Analyst you can analyze a requirement within the context of an online phone bill payment application. 𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭: The online phone bill payment application shall allow users to set up automatic recurring payments for their monthly phone bills. 𝐀𝐧𝐚𝐥𝐲𝐬𝐢𝐬 𝐁𝐫𝐞𝐚𝐤𝐝𝐨𝐰𝐧: 𝐄𝐥𝐢𝐜𝐢𝐭𝐚𝐭𝐢𝐨𝐧 𝐚𝐧𝐝 𝐂𝐨𝐥𝐥𝐚𝐛𝐨𝐫𝐚𝐭𝐢𝐨𝐧: 1. The BA interview users to understand their preferences for automatic payments (frequency, payment methods, notification preferences). 2. Gather a group of potential users to discuss their expectations and pain points related to recurring payments. 3. Research other online payment platforms to see how they handle automatic payments and identify best practices. 𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭𝐬 𝐀𝐧𝐚𝐥𝐲𝐬𝐢𝐬 𝐚𝐧𝐝 𝐃𝐞𝐬𝐢𝐠𝐧 𝐃𝐞𝐟𝐢𝐧𝐢𝐭𝐢𝐨𝐧: Break down "automatic recurring payments" into smaller components: 1. Frequency options (monthly, bi-weekly, etc.) 2. Payment method options (credit card, bank account) 3. Payment date options (fixed date, due date, custom date) 4. Notification options (email, text message) 5. Confirmation options (receipt, payment history) Create use case diagrams: Illustrate the different scenarios and interactions involved in setting up and managing automatic payments (e.g., user logs in, selects payment method, sets frequency, confirms payment). Define acceptance criteria: 1. The system shall allow users to set up recurring payments for any supported phone carrier. 2. The system shall send a confirmation email/text message to the user after each successful automatic payment. 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧 𝐄𝐯𝐚𝐥𝐮𝐚𝐭𝐢𝐨𝐧: 1. Work with developers to assess the technical feasibility of implementing the recurring payment feature, considering factors like security requirements and integration with payment gateways. 2. Identify potential risks, such as unauthorized access to payment information or failed payments, and develop mitigation strategies. Validation and Verification: 3. Present the analyzed requirements and design recommendations to stakeholders, including product owners, developers, and user representatives, for feedback and approval. 4. Create interactive prototypes of the automatic payment setup process to gather user feedback and identify any usability issues. 5. Develop and execute test cases to verify that the automatic payment feature functions as expected and meets the defined acceptance criteria. BA Helpline #businessanalysis #businessanalyst #businessanalysts #ba #requirements #analysis