When does class start/end?
Classes begin promptly at 9:00 am, and typically end at 5:00 pm.
Utilizing an Agile approach effectively requires more than just ensuring the development team is following the Agile process, it is a collaborative effort between this team and the product owner. Agile represents a true paradigm change for most organizations, and in order to truly take advantage of the possible benefits, today's product owners need to know how to support their development partners. The Agile for Product Owners training course will provide extensive knowledge and understanding of the principles of Agile, demonstrate how to use the product backlog as a tool for driving successful product outcomes, clearly instructs ways of working in partnership with the development organization, and provide tools that enable teams to embrace the change required for delivering the best products possible.
More than simply a methodology or approach to software development, Agile embraces a set of principles that drive more effective software development. Agile focuses on the customer, embraces the ever changing nature of business environments and encourages human interaction in delivering outstanding software. In this introduction, we'll discuss the following:
Agile Teams embrace cross-functional collaboration and understand that the individual succeeds only when the team succeeds. We will discuss how to form the Agile Team, appropriate teams size, how the Product Owner fits in, as well as the following topics:
The Product Owner plays an integral role on an Agile Team. Without the input and direction from the PO, the team makes assumptions and often inappropriate decisions about the product that are not aligned with what the customer actually wants. Here we will discuss the role of the Product Owner, how they provide direction for the team and how they engage with the team to allow the right product emerge for the right customers.
The Agile framework embraces a methodical process of planning that goes into 5 levels of detail. Rather than mistakenly getting to the details too soon of ever-changing requirements, Agile planning helps us focus on the right level of detail for the right priorities at the appropriate time. In this section we'll cover the following:
It is critical that the customer be the focus of a product throughout the development lifecycle. Every requirement should bring some value to the customer. Therefore, prior to defining requirements, it is important to define the customer. This will include the following topics:
The Product Backlog is the complete list of desired elements, or requirements, for the product. It consists of User Stories (requirements from a customer point of view), Foundational Stories and any other work items the team must complete. Stories do not capture all of the detailed requirements, but require enough information to estimate, plan and facilitate verbal requirements discussions at the appropriate time.. In this section we will explore the following:
Since we build the Product Backlog through the utilization of User Stories, we will talk through some guidelines and tips for writing effective User Stories, how to break them down when necessary and how to clearly identify requirements valuable to users.
The Product Roadmap describes the sequence of product releases to make the product strategy a reality. In this section we will talk about grouping User Stories into Product Themes and how to organize those themes into a high level plan providing direction and visibility for the team, management and stakeholders.
Prioritization is often done at a level that excludes the development team and fails to account for the technical expertise the team provides in determining dependencies, impact, risk and the sequencing of work items. In this section we explore methods of prioritization and how PMs can help the business and development groups collaborate together to determine the right priorities. We will peruse the following topics:
Among the greatest challenges in developing software and delivering against stakeholder expectations is estimating accurately and subsequently planning how those expectations can be met. Agile cannot make that challenge disappear, but offers some very helpful tools that enable teams to set and meet the appropriate expectations. Product Owners should understand their role in the estimating process providing direction and product details to the team.
The release plan identifies a goal for the stories that will be included for a release of the software. Through the prior processes, the team will have prioritized the stories and estimated the team velocity. These key elements will come together to give the team a level of confidence that they can deliver the necessary requirements for a product release in what is normally a fixed timeframe. We'll examine the following topics:
At the appropriate time, prior to entering into the development of a story, requirements will need to be discussed in more detail. The instructor will introduce several methods for helping Product Owners lead their teams in "getting to the details" of Agile Requirements.
An iteration is a fixed amount of time in which stories/requirements will be developed, tested and ready for release. Product Owners need to understand how to engage the team and provide the necessary direction to effectively break out the tasks, hours and assignments for the Iteration. We'll also discuss how POs can be engaged with the team as they execute the Iteration and provide the right deliverables and measurements to help you make decisions about the product.
The Retrospective is one of the key practices of Agile and is the inspect and adapt mechanism for the team. Product Owners should help the team identify what is working, what is not working and what specific areas need to be improved.
This last section is where we bring everything together and discuss specific implementation strategies, how to overcome resistance and several additional tips to effectively manage Product Development Cycles in an Agile environment. Topics covered include:
Classes begin promptly at 9:00 am, and typically end at 5:00 pm.
Lunch is normally an hour long and begins at noon. Coffee, tea, hot chocolate and juice are available all day in the kitchen. Fruit, muffins and bagels are served each morning. There are numerous restaurants near each of our centers, and some popular ones are indicated on the Area Map in the Student Welcome Handbooks - these can be picked up in the lobby or requested from one of our ExitCertified staff.
If someone should need to contact you while you are in class, please have them call the center telephone number and leave a message with the receptionist.
Most courses are conducted in English, unless otherwise specified. Some courses will have the word "FRENCH" marked in red beside the scheduled date(s) indicating the language of instruction.
GTR stands for Guaranteed to Run; if you see a course with this status, it means this event is confirmed to run. View our GTR page to see our full list of Guaranteed to Run courses.
We have training locations across the United States and Canada. View a full list of classroom training locations.
Yes, we provide training for groups, individuals and private on sites. View our group training page for more information.
Yes, we provide training for groups, individuals, and private on sites. View our group training page for more information.
It was a pleasant experience from registration all through the course. I just wish they would have covered 100% of the material covered by the exam.
First remote course and I am pleasantly surprised. Love the on site facilities in Ottawa, but the online course format was very well received.
The course was very thorough and the instructor ensured that all the students were on the same page.
ExitCertified provided the participants with all the required information we needed to join the training one week in advance and ensured that we had all the required materials to make the experience as seamless as possible.
Very clear and concise course. It was worth attending to me and provided useful information I will use going forward.
13 options available