Automation Project 2: Gathering requirements

Overview: Why Requirement Gathering is the Silent Killer of RPA

In my decade plus in the tech world, I’ve seen more real-world projects fail because of poor communication than because of bad code. Automation Project 2: Gathering Requirements tackles the most volatile part of the RPA lifecycle: the human element. Most beginners want to jump straight into UiPath or Blue Prism and start dragging-and-dropping activities, but this course forces you to slow down and realize that if your requirements are “garbage in,” your automation will be “garbage out.”

This isn’t just a dry lecture on documentation. It’s a deep dive into Stage 2 of the 6-stage RPA process, focusing on the “Discovery” and “Analysis” phases. What I appreciated most was the focus on the PDD (Process Definition Document) and BRD (Business Requirements Document). These aren’t just acronyms; they are the contracts between you and the business. The course does an excellent job of teaching you how to translate “I spend three hours a day copying data from Excel” into a technical roadmap that a developer can actually execute. It’s about bridge-building, and quite frankly, it’s a skill that separates the junior hobbyists from the high-earning Solution Architects.

The curriculum pushes the MoSCoW method—Must have, Should have, Could have, and Won’t have—as a survival tactic. In the real world, stakeholders want the moon, the stars, and a coffee machine built into their bot. This course teaches you how to manage those expectations and prioritize what actually drives ROI. It’s an honest, gritty look at the administrative side of tech that most “learn to code” bootcamps conveniently ignore.

Who Should Step Into This?

This isn’t exactly a “zero to hero” course for someone who doesn’t know what a computer is, but it is built for the beginner to advanced spectrum. If you’ve finished “Project 1” or have a baseline understanding of what Robotic Process Automation is, you’re ready. It’s specifically geared toward those who want to pivot into RPA Business Analyst or Project Manager roles where job-ready skills involve more talking and strategy than actual scripting.

• Familiarity with the general RPA project lifecycle.
• Basic understanding of business processes (how a bill becomes a payment, etc.).
• A desire to move beyond “just coding” into automation strategy.

The Toolkit: More Than Just Spreadsheets

While you won’t be writing Python scripts here, you are mastering industry-standard tools and frameworks that are arguably more valuable for career growth. The “labs” here involve mental gymnastics and documentation precision.

• Document Authoring: Mastering the structure of the Business Requirements Document (BRD).
• Process Mapping: Building out the Process Requirements Document (PRD)—the literal “bible” for the bot.
• Prioritization Frameworks: Implementing MoSCoW to manage scope creep.
• Stakeholder Interviewing: Techniques to extract “hidden” steps from employees who perform tasks subconsciously.
• Quality Control: Learning how to write “SMART” requirements that are testable and unambiguous.

The Payoff: Job Roles and Market Value

Let’s talk money. Companies are desperate for people who can bridge the gap between “Business” and “IT.” Completing this course and the broader certification prep associated with this series puts you on the map for high-paying roles. You aren’t just a “bot builder”; you are a Digital Transformation Consultant. This course prepares you for roles such as:

• RPA Business Analyst: The person who decides what gets automated (Average salary is often 20% higher than standard BAs).
• Implementation Lead: Managing the 6-stage lifecycle from start to finish.
• Solution Architect: Designing the high-level flow before the developers touch it.
• Operations Manager: Streamlining internal real-world projects to save thousands of man-hours.

The Pros: What They Got Right

• No Fluff Strategy: It ignores the hype and focuses on the “boring” stuff that actually makes or breaks a project. This is hands-on labs for your brain, teaching you how to think logically about messy human processes.
• Stakeholder Nuance: I loved the section on “hearing all voices.” In RPA, if you ignore the person actually doing the work, they will find a way to break your bot. The course teaches you the soft skills needed for career growth.
• High-Quality Templates: You walk away with a clear understanding of what a professional-grade BRD and PDD should look like. You can take these insights directly into a job interview and sound like a seasoned pro.

The Cons: The Honest Reality

• Documentation Heavy: If you are someone who hates writing and just wants to see code run, you’re going to find this tedious. There are no “quick wins” or flashy visuals here—it’s about the grind of gathering requirements. However, it is a necessary evil if you want to avoid 3:00 AM emergency bug fixes later.