This course begins with the fundamentals of the requirements process, including project definition template, the uncertainty of requirements, nailing down stakeholders, and the skills needed to be a requirements analyst. Next we explore how requirements gathering in an Agile environment works. And lastly, we review practical tools to guide the student from user cases/stories, work flows, mockups, business rules, and data model to produce a solid specification that meets a customer's expectations. This course covers the following PMBOK® Process Groups: Planning, Executing, Monitoring and Controlling. This course covers the following PMBOK® Knowledge Areas: Project Scope Management, Project Communications Management, Project Stakeholders Management.
Michael is General Manager at Fairway Technologies, a San Diego based technology consulting company. Prior to that, he was Vice President of Development at PDSA, Inc. and has many years of management, technology, and leadership experience.
Fundamentals Hello, I am Michael Krasowski from Pluralsight. I will be presenting the course Best Practices for Requirements Gathering. Best Practices of Requirements Gathering is comprised of three modules. The first is Fundamentals, followed by Practical Tools, and lastly, Requirements Gathering in an Agile Environment. Have you ever wondered why your applications or systems just don't seem to meet your customer's expectations? This module will provide you with the fundamental understanding of the challenges of gathering requirements. The following topics will be covered in the overview to this module. Why process is critical to your success. The project triangle dilemma. Understanding the balance of scope, budget, and schedule. Know your desired result before your embark on your project. The project definition template. Don't leave home without it. Structure and the right level of effort. One process or tool does not fit all projects. Gathering requirements is hard work. Continuous customer involvement is critical. Know your stakeholders. Most projects have a diverse set of stakeholders, get to know them well. Effective communication is essential to being an effective analyst and translating business objectives into succinct requirements. Are you up for the job? Do you have what it really takes? Can you make the transition from software engineer to requirements analyst? Stay tuned. The uncertainty of business requirements. Business requirements will always have degrees of uncertainty and we will learn how to adapt to this.
Practical Tools Hello, I'm Michael Krazowski from Pluralsight. I will be presenting the module "Practical Tools" in the course "Best Practices of Requirements Gathering". Practical Tools: Module Overview. This module discusses several simple and practical tools that can easily help you be better at gathering requirements. User stories. Use cases. Prototypes. Wireframes. Mockups. Work Flow Diagrams. Swim lanes. Database Models. Business Rule Specifications. These items collectively make up the core results of your Requirements Gathering Process.
Requirements Gathering in an Agile Environment Hello, I'm Michael Krasowski from Pluralsight. I will be presenting the module, Requirements Gathering in an Agile Environment, in the course, Best Practices of Requirements Gathering. Requirements Gathering in an Agile Environment: Module Overview. We will be covering the following topics in the context of your role of gathering requirements. First, Agile Myths: Let's understand and dispel those misunderstandings. The Agile Process and Philosophy: Just a quick primer here. Basic Terms used by most Agile methodologies. How to create and manage a Product Backlog. Release Planning and Roadmaps and their importance. User's Perception of Agile and how it may affect your success. Why Agile Makes Users Nervous. Educate your Users so they hopefully won't be so unsure and cautious about Agile. Key Collaboration Factors: These are key communication soft skills you need to know. And lastly, the Summary. Requirements Gathering in an Agile Environment. In the first module we learned about the fundamentals of requirements gathering. In the second module we learned about several practical tools to help you gather requirements. In this module, we will provide some context in how requirements gathering can work within an Agile environment. Every environment is different-with several 'shades of gray' as to how agile they might be, maybe not agile at all. We will explore some requirements gathering techniques that can assist you regardless of the amount of agility that may exist in your environment.