Scrum Product Owner Workshop: In-House Training The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. The Product Owner must be knowledgeable, available, and empowered to make decisions quickly in order for an Agile project to be successful. The Product Owner's key accountability is the Product Backlog. Managing, maintaining, and evolving the Product Backlog involves: Establishing a clear Vision that engages the Development Team and stakeholders Clearly expressing Product Backlog items Ordering the items in the Product Backlog to best achieve the Vision and goals Ensuring that the Product Backlog is visible, transparent, and clear to all Working with the Development Team throughout the project to create a product that fits the customer's needs The overall course goal is to support you in becoming an effective Product Owner. What you will Learn You'll learn how to: Differentiate between poor, good, and great Product Owner attributes, and their impact on the team, product, stakeholders, and the organization Engage your stakeholders by knowing your customers and market Develop an effective and value-driven Product Backlog Evaluate the Product Owner's role in Scrum's 5 events and team engagement Foundation Concepts Agile foundation Product owner role Product Ownership Product ownership Project vision Understanding your customers and market Personas Stakeholder management and engagement The Product Backlog Epics and user stories Preparing user stories for a sprint The product backlog Visualizing the product backlog Product backlog prioritization Technical debt Sprint Planning and Delivery Sprint planning The sprint Sprint Reviews, Retrospectives, and Closing Sprint reviews Key agile patterns Retrospectives Closing the project
Agile and Scrum Fundamentals: In-House Training The overall goal of the course is to provide learners with the fundamentals of what Agile and Scrum are, and how to effectively apply Agile methods in your projects. What you will Learn At the end of this program, you will be able to: Describe Agile and Scrum foundation concepts Compare and contrast Agile roles to traditional roles Initiate an Agile project Develop Release Plans Build an Iteration Plan Execute an Iteration Implement Agile in your environment Getting Started Introductions Workshop orientation Expectations Foundation Concepts Project Lifecycles What is Agile? Why Agile? A range of Agile methods Focus on Scrum The People Side of Agile A range of Agile roles Focus on Scrum roles Unique characteristics of Agile Teams Building effective Agile Teams Initiating an Agile Project Conducting Sprint Zero Setting the vision Building the Product Backlog and User Stories Defining Acceptance Criteria Planning Releases Planning releases Estimating user stories Prioritizing user stories Selecting a Sprint length Estimating velocity Creating a release plan Planning an Iteration Conducting the Sprint Planning Meeting Building the Sprint Backlog Creating a Sprint Plan Running an Iteration Executing Sprint activities Using Burn-down and Burn-up Charts Negotiating changes during a Sprint Conducting the Sprint Review Meeting Implementing Agile Conditions of success for implementing Agile and Scrum Implementing Agile Final words
Microsoft Project Blue Belt® 2016: In-House Training This course introduces Project Server 2016 features that expedite scheduling projects and simplify managing tasks within an enterprise environment. Learn different aspects of Project Server and their benefits to varying roles in the enterprise, and gain hands-on experience and insights on best practices from SMEs around the world. This course introduces Project Server 2016 features that expedite scheduling projects and simplify managing tasks within an enterprise environment. Learn different aspects of Project Server and their benefits to varying roles in the enterprise, and gain hands-on experience and insights on best practices from SMEs around the world. Users in Project online will get the same benefits of this program. What you Will Learn You'll learn how to: Describe the Enterprise Project Management (EPM) environment Apply the basic project management principles of, initiating, planning, executing, monitoring and controlling, and closing your project schedules Discuss new features Explain PWA views project sites Meet deadlines and budget restrictions Keep the workloads of your resources within their available limits Explain tracking methods and manage task assignments Update the schedule Differentiate between updating tasks and timesheets Use standard reports, custom views, and visual reports for your projects Recognize the potential of the Business Intelligence features Getting Started with Microsoft® Project Server 2016 Describing the EPM context Discovering Project Web App Differentiating the users of PWA Working with Project Professional and PWA Initiating Projects New projects with Project Professional, SharePoint lists, Enterprise Projects Importing schedules and managing project owner and permissions Customize the ribbon with enterprise commands Planning Projects - Scope and Schedule Management Scheduling in PWA Using the Deliverables feature Developing components of the risk management plan and issues tracking Linking planning documents Planning Projects - Staffing Management Plan Building a project team Managing resource availability Reviewing the assignment cycle Managing resource engagements Resolving resource overallocation Executing, Monitoring and Controlling Baselines Working with timesheets Reporting administrative time Tracking methods (% work, actual work, single entry mode) Assignment progress and updates in PWA Task progress and updates in Project Professional and PWA Monitor and Control Projects - Measuring Performance and Reporting Progress Reviewing performance metrics and progress reports Using the preloaded reports at the Business Intelligence Center Considerations for defining custom reports Closing Projects Reviewing the closing processes and closing tasks to updates Supporting the closing process
Assuring Quality Through Acceptance Testing: In-House Training It is also the business analyst's responsibility to confirm that the resulting solution developed by IT does, in fact, solve the defined problem. This is done first through testing, especially acceptance testing, and then through monitoring of the installed solution in the user community. It is the business analyst's job to define the business problem to be solved by IT. It is also the business analyst's responsibility to confirm that the resulting solution developed by IT does, in fact, solve the defined problem. This is done first through testing, especially acceptance testing, and then through monitoring of the installed solution in the user community. The business analyst is not only concerned with the testing itself, but also with the management and monitoring of the users doing the acceptance testing, and recording, analyzing, and evaluating the results. What you will Learn Upon completion, participants will be able to: Create a set of acceptance test cases Manage and monitor an acceptance test stage where users perform the testing Work with the development team in the systems testing stage Assess the solution once it is in the business environment Foundation Concepts The role of the business analyst An introduction to the BABOK® Guide BA roles and relationships through the project life cycle Introduction to assuring software quality through acceptance testing The Scope of IT Testing Overview of testing stages The testing process Testing documentation Pre-Acceptance Testing The BA's role in testing Early development testing stages (unit and integration) Late development testing stage (system) The Acceptance Test Stage - Part I (Planning, Design, and Development) Overview of user acceptance testing Acceptance test planning Designing user acceptance tests Developing individual user acceptance test cases Building effective user acceptance test scenarios The Acceptance Test Stage - Part II (Execution and Reporting) Operating guidelines Execution Reporting Post-Acceptance Testing Overview Project implementation Project transition (project closure) Production through retirement Testing Commercial Off-the-Shelf (COTS) Software Overview Selecting the software Implementing the software Summary What did we learn and how can we implement this in our work environments?
Project Accounting and Finance Skills: In-House Training Do you manage both project schedules and budgets, but do not have insight into how actual results relate to the approved budget? Do you desire to have more clarity about the relationship between your project's performance with the accounting and financial systems in your organization? Do you need to understand financial and accounting terminology to bridge the gap between the 'world of finance' and the 'world of project management? Organizations have a need to manage-by-projects, because projects are the means to deliver on strategic goals and objectives. Therefore, the project manager must have an understanding of the financial world of investments to ensure the organization will realize expected business value. This requires a foundation in the principles of accounting and finance to comprehend how the project's contribution provides an organization with a competitive advantage. Learn what you must do to give your organization the assurance it needs that its investment in your project will realize business value. Learn what you must do to give your organization the assurance it needs to know that its investment in your project will realize business value. What You Will Learn At the end of this program, you will be able to: Explain the aspects of classical corporate accounting and finance effects on managing projects Determine how your project fits into the corporate income statement, balance sheet, and cash flow statement Analyze the financial aspects of managing projects Use earned value management as the basis for decision making throughout the project life Recognize the importance of the project manager's financial responsibilities Focus on what PMs do and should be doing, in support of accounting and finance Use financial information within a project environment to meet financial results Track and analyze the project's financial status and forecast with the goal of realizing benefits Generate work performance data to ensure a project's outcome aligns with financial metrics Foundation Concepts Accounting and Finance Terms and Concepts Accounting and Finance Essentials Financial Terms and Concepts Projects as Financial Investments Overview of 'Two Worlds' Project as Investments Accounting and Finance World: Standards, Principles and Practices Accounting and Finance Standards and Principles Accounting and Finance Practices Capital Budgeting Corporate Budgeting Accounting and Finance World: Economic Project Selection Methods Economic Project Selection Methods Economic Project Selection and the Business Case Project Management World Project Management and Financial Controls Project Management and Work Performance Data Project Management and Earned Value Management Project Management and Work Performance Reporting
Recovering Troubled Projects: In-House Training Despite our best intentions, many of the projects that organizations undertake either don't achieve their intended business results or end in complete failure. Most seasoned project managers have had their share of experiences with difficult or troubled projects and unless they are careful, they will encounter more. This workshop does not focus on 'failed' projects but rather on those projects which without appropriate intervention would be headed for failure. Failed projects are those beyond help and which should be terminated. Here we focus on projects that are salvageable. It is an exercise-driven, no-nonsense, professional practice-focused workshop positioning the participant to immediately apply the tools and lessons learned in the classroom. The workshop employs the use of both illustrative and practical/working case studies. Illustrative case studies will examine insights from real-world troubled projects. Participants will be asked to bring descriptions of their own examples of troubled projects on which they're currently working or on which they have worked in the past. A number of these will be used as the basis for the practical/working case studies. The approach builds on and complements the disciplines addressed in Project Management Institute's PMBOK® Guide and also addresses issues that arise when managing projects in a complex environment. What You Will Learn You will learn to: Recognize the value of a structured project recovery process Explain the reasons most projects fail Analyze the causes of a project's troubles Construct a negotiation process to use with key stakeholders Apply an effective strategy to planning the recovery effort Manage, evaluate, and adjust the ongoing recovery effort Foundation Concepts Recognizing a troubled project Defining the project recovery process The Reasons Projects Fail Putting failure in perspective Reviewing management issues Analyzing planning issues Exploring complexity issues Assess the Project Stabilizing the project Determining preliminary Go / No-Go Conducting a detailed recovery assessment Negotiate the Recovery Reviewing the basics of negotiation Setting reasonable expectations Obtaining appropriate PM authority Securing key stakeholder support Plan the Recovery Planning for recoveries Rebuilding the project team Reshaping the project plan Managing parallel activities Planning for change management Implement and Adjust the Project Implementing project recoveries Facilitating change Enabling continuous learning Fostering the project team Sustaining stakeholder engagement
Project Management Fundamentals for IT Projects: In-House Training A number of factors impact the new project manager's role within IT - for instance, the need to fully integrate IT into the business improvement process and the advent of distributed technology and Business Process Reengineering. As a result, the range of activities required of a new project manager has greatly increased, as well as the range of people with whom he or she interacts. This workshop enables you to minimize the problems inherent in managing a systems development project. What You Will Learn You'll learn how to: Articulate the benefit of using a project management methodology, processes, and various life cycles for IT projects Articulate on various standards and maturity models that provide benefits to performing organizations that manage IT projects Describe governance, gating, and the processes required for project origination Conduct a stakeholder analysis and describe its benefits throughout the project life cycle Gather good requirements, develop a work breakdown structure (WBS), and establish a baseline project plan Execute against the baseline project plan while managing change and configuration items Monitor and control the project activities using the baseline project plan and earned value management concepts Close the project by conducting scope verification, procurement audits, gathering lessons learned, archiving project records, and releasing resources Getting Started Course goal Course structure Course goals and objectives Foundation Concepts Key definitions and concepts Methodologies, processes, and project life cycles Project success factors and the benefits of standards and models Project Originating and Initiating Originating projects Initiating projects Planning Stakeholder Engagement and Resource Management Planning stakeholder engagement Planning human resources management Developing effective leadership skills Planning Scope and Quality Management Planning project scope Planning project quality Planning Schedule Management Planning project time Identifying schedule activities Sequencing schedule activities Estimating activity resources and time Developing project schedule Optimizing the project schedule Planning Risk and Cost Management Planning for project risks Planning project costs Estimating project costs Developing a project budget Planning Communication and Procurement Management Planning project communications Planning project procurements Project Executing, Monitoring and Controlling, and Closing Project executing Project monitoring and controlling Project closing
Developing the Business Case: In-House Training Business analysts must be able to create business case documents that highlight project benefits, costs, and risks. The business case is based on the real business need to be solved. These become parts of proposals, feasibility studies, and other decision support documents. This course teaches the purpose, structure, and content of a business case. It presents the basic techniques for determining financial ROI, non-tangible benefits, and the probability of meeting expectations. What you will Learn At the end of this program, you will be able to: Perform feasibility studies Justify the business investment to solve the business problem Prepare an effective business case document Plan and implement a business case approval process Foundation Concepts The role of the BA An introduction to the BABOK® Guide The business analyst and the product / project life cycle (PLC) The business case deliverable Introducing the Business Case Process The BA and strategy analysis The BA and the business case process (BCP) The BA during the business case process (BCP) The BA after the business case process (BCP) Importance of defining solution performance metrics Defining the Business Need Overview of defining the business need Business needs: problem / opportunity statement Product vision Objectives and constraints Exploring Business Case Solutions Overview of exploring solutions Solution identification for feasibility Solution definition for analysis Assessing project risks Justifying the Business Case Overview of justifying the business case Qualitative justification Quantitative justification Approving the Business Case Overview of business case approval Developing recommendations Preparing the decision package - documents Preparing the decision package - presentations
Agile Release Plans: In-House Training While many Agile frameworks provide guidance on a focus on value and iterative development, many do not explain how that value is delivered to the customer. Release Plans have become an accepted and common practice to bridge the gap between the Product Vision and the Product Backlog (Agile requirements). In this course, you will be provided with an introduction to Agile and to Scrum, the most utilized Agile framework. You will also learn how the Vision, Roadmap, and Charter help to establish the Release Plan. The goal of this course is to equip you with the necessary knowledge, skills, and techniques to build Release Plans to ensure you deliver the most value to your customers. What you will Learn At the end of this program, you will be able to: Recall the Scrum framework elements (roles, events, and artifacts) Examine the benefits of Agile Develop a Product Vision and Roadmap Create an Agile Project Charter Prepare a Release Plan Write user stories to support a Product Backlog Foundation Concepts Introduction to Scrum Scrum Overview Agile Benefits Product Definition Business Goals Product Vision Product Roadmap Agile Project Charter Product Scope Project Risks Release Deadlines Sprint Durations Team Norms Release Planning Release Plan Process Select Stories and a Release Date Product Backlog User stories Building the product backlog Product Backlog Refinement Transitioning to the Scrum Team
Scrum Master Workshop: In-House Training A Scrum Master helps project teams properly use the Scrum framework, increasing the likelihood of the project's overall success. Scrum Masters understand Scrum values, practices, and applications and provide a level of knowledge and expertise above and beyond that of typical project managers. Scrum Masters act as 'servant leaders', helping the rest of the Scrum Team work together and learn the Scrum framework. Scrum Masters also protect the team from both internal and external distractions. What you will Learn You'll learn how to: Comprehend the Agile Manifesto and mindset Explain the fundamental principles of Scrum Guide the Scrum team in their responsibilities Write requirements in the form of user stories Define Ready and Done Estimate using planning poker and prioritize using MoSCoW Facilitate the team through the 5 Sprint events Fulfill the role of Scrum Master in a Scrum project Create Information Radiators to enable transparency Define the structure of the retrospective Foundation Concepts Agile History, Values, and Mindset Introduction to Scrum Scrum events Scrum artifacts Scrum Roles and Responsibilities Product Owner responsibilities Scrum Master responsibilities The Team responsibilities Cross-functional Teams Building Effective Teams The Product Backlog and User Stories The Product Backlog User Stories Definition of Done Backlog grooming Estimating User Stories Story points, planning poker Prioritizing User Stories The Sprint Team capacity and velocity The Sprint Planning Meeting The Sprint Backlog The Sprint Learning to self-manage, self-organize, self-improve Sprint Review and Retrospective Project Progress and Completion The Daily Scrum The Task Board and The Burndown Chart Information Radiators Closing a Scrum Project Summary and Next Steps Review of course goals, objectives, and content