Disruptive Leadership: Delivering Twice the Work in Half the Time Disruptive Leadership: Delivering Twice the Work in Half the Time Abstract: The inventor and co-creator of Scrum will describe its origins in military strategy, medical research on complex systems, and its application in product development and other domains such as education and defense. This and other IIL Learning in Minutes presentations qualify for PDUs. Some titles, such as Agile-related topics may qualify for other continuing education credits such as SEUs, or CEUs. Each professional development activity yields one PDU for one hour spent engaged in the activity. Some limitations apply and can be found in the Ways to Earn PDUs section that discusses PDU activities and associated policies. Fractions of PDUs may also be reported. The smallest increment of a PDU that can be reported is 0.25. This means that if you spent 15 minutes participating in a qualifying PDU activity, you may report 0.25 PDU. If you spend 30 minutes in a qualifying PDU activity, you may report 0.50 PDU.
Scrum Product Owner Exam Prep: In-House Training: Virtual In-House Training This workshop prepares you for the Scrum.org PSPO™ I certification. A voucher for the exam and the access information you will need to take the exam will be provided to you via email after you have completed the course. NOTE: If you have participated in any of IIL's other Scrum workshops, you can bypass this program and focus on reading/studying the Scrum Guide and taking practice exams from Scrum.org 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 need The Professional Scrum Product Owner™ I (PSPO I) certificate is a Scrum.org credential that enables successful candidates to demonstrate a fundamental level of Scrum mastery. PSPO I credential holders demonstrate an intermediate understanding of the Scrum framework, and how to apply it to maximize the value delivered with a product. They will exhibit a dedication to continued professional development, and a high level of commitment to their field of practice. Scrum.org does not require that you take their own sponsored or any preparatory training. However, training can facilitate your preparation for this credential. And this course is based on IIL's Scrum Product Owner Workshop, which is aligned with The Scrum Guide™. It will provide you with the information you need to pass the exam and IIL will make the arrangements for your online exam. You will be provided with an exam code and instructions, so that you can take the exam at your convenience, any time you are ready after the course. Passwords have no expiration date, but they are valid for one attempt only. See additional exam details on the next page. What you will Learn You'll learn how to: Successfully prepare for the Scrum.org PSPO I exam Identify the characteristics of a successful Product Owner Create a powerful vision statement Apply techniques to understand your customers and the market Manage and engage stakeholders Write effective user stories with acceptance criteria Utilize techniques to visualize and prioritize the Product Backlog Participate in the 5 Scrum events as the Product Owner Understand the Product Owner's role in closing a Scrum project Getting Started Introductions Workshop orientation Exam prep preview Fundamentals Recap Agile Manifesto, values, and mindset Product Owner characteristics Good vs. great Product Owner Product Ownership Product ownership Project vision Understand your customers and market Personas Stakeholder management and engagement The Product Backlog User Stories and Acceptance Criteria Preparing User Stories for a Sprint The Product Backlog Visualizing the Product Backlog Product Backlog Prioritization Technical Debt Sprint Planning and Daily Standups Sprint Planning Planning Poker Team Engagement Daily Standups Sprint Review, Retrospectives, and Closing Sprint Reviews Key Agile Patterns Retrospectives Closing the Project Summary and Next Steps Review of course goals, objectives, and content Exam prep next steps
Scrum Master Workshop: In-House Training: Virtual 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
Leading in a Disruptive Age: Don´t Just Manage Projects ... Lead Them How can a leader in today's organization get the right mix across teams, leadership, and the culture that binds them together? This session will cover the latest trends in what drives teams, the disconnects between leaders and their teams, and considerations for building a winning project culture that drives value to both the customer and organization across factors of people, process, and technology. This and other IIL Learning in Minutes presentations qualify for PDUs. Some titles, such as Agile-related topics may qualify for other continuing education credits such as SEUs, or CEUs. Each professional development activity yields one PDU for one hour spent engaged in the activity. Some limitations apply and can be found in the Ways to Earn PDUs section that discusses PDU activities and associated policies. Fractions of PDUs may also be reported. The smallest increment of a PDU that can be reported is 0.25. This means that if you spent 15 minutes participating in a qualifying PDU activity, you may report 0.25 PDU. If you spend 30 minutes in a qualifying PDU activity, you may report 0.50 PDU.
Humble Leadership: Servant Leadership in Practice With traditional project management, we've become accustomed to a 'command and control' leadership style. According to the Greenleaf Center for Servant Leadership, servant leadership is a philosophy and set of practices that enriches the lives of individuals, builds better organizations, and ultimately creates a more just and caring world. Let's explore how adopting a servant leadership stance with our Scrum Team can create a more collaborative and engaged team. This and other IIL Learning in Minutes presentations qualify for PDUs. Some titles, such as Agile-related topics may qualify for other continuing education credits such as SEUs, or CEUs. Each professional development activity yields one PDU for one hour spent engaged in the activity. Some limitations apply and can be found in the Ways to Earn PDUs section that discusses PDU activities and associated policies. Fractions of PDUs may also be reported. The smallest increment of a PDU that can be reported is 0.25. This means that if you spent 15 minutes participating in a qualifying PDU activity, you may report 0.25 PDU. If you spend 30 minutes in a qualifying PDU activity, you may report 0.50 PDU.
Leadership Principles for Projects Success We all need and thrive on successful projects. But what does it take to get there? This session outlines five simple yet powerful leadership principles which can help you pave the path to project success. This and other IIL Learning in Minutes presentations qualify for PDUs. Some titles, such as Agile-related topics may qualify for other continuing education credits such as SEUs, or CEUs. Each professional development activity yields one PDU for one hour spent engaged in the activity. Some limitations apply and can be found in the Ways to Earn PDUs section that discusses PDU activities and associated policies. Fractions of PDUs may also be reported. The smallest increment of a PDU that can be reported is 0.25. This means that if you spent 15 minutes participating in a qualifying PDU activity, you may report 0.25 PDU. If you spend 30 minutes in a qualifying PDU activity, you may report 0.50 PDU.
Estimating for Business Analysts: In-House Training A business analyst does not have authority to estimate the project and will not be held responsible for the project staying within the proposed budget; however, the business analyst does participate in various planning exercises with the project team. Many times the business analyst is on his or her own, required to provide estimates of how long it will take to perform their tasks. This course acquaints you with the basics of estimating from the point of view of the business analyst, emphasizing time estimates for the work. It also covers some of the product cost estimates that a business analyst may have to provide when the business is performing a cost/benefit analysis for the project. What you will Learn You'll learn how to: Translate business needs and requirements into estimates Estimate durations using a variety of techniques Negotiate differences in estimates Getting Started Introductions Course structure Course goals and objectives Foundation Concepts The importance of estimating to a business analyst The good and bad of estimating The project context The meaning of good estimating Focuses of estimating Characteristics of a good estimate Estimating the Time Requirements Applicable BABOK® Knowledge Areas Business Analysis Planning and Monitoring Elicitation and Collaboration Estimating the elicitation Information Gathering Plan Relative times for elicitation activities Planning and estimating the business analysis approach and activities Planning the business analysis activities Impact of process Estimating the Product Estimating the value of the product Business analyst's role Defining and determining value Function and use case points Agile estimating Planning Poker Other agile estimating techniques Negotiating estimates Negotiation techniques Negotiation approaches Summary What did we learn, and how can we implement this in our work environment?
Estimating for Business Analysts A business analyst does not have authority to estimate the project and will not be held responsible for the project staying within the proposed budget; however, the business analyst does participate in various planning exercises with the project team. Many times the business analyst is on his or her own, required to provide estimates of how long it will take to perform their tasks. This course acquaints you with the basics of estimating from the point of view of the business analyst, emphasizing time estimates for the work. It also covers some of the product cost estimates that a business analyst may have to provide when the business is performing a cost/benefit analysis for the project. What you will Learn You'll learn how to: Translate business needs and requirements into estimates Estimate durations using a variety of techniques Negotiate differences in estimates Getting Started Introductions Course structure Course goals and objectives Foundation Concepts The importance of estimating to a business analyst The good and bad of estimating The project context The meaning of good estimating Focuses of estimating Characteristics of a good estimate Estimating the Time Requirements Applicable BABOK® Knowledge Areas Business Analysis Planning and Monitoring Elicitation and Collaboration Estimating the elicitation Information Gathering Plan Relative times for elicitation activities Planning and estimating the business analysis approach and activities Planning the business analysis activities Impact of process Estimating the Product Estimating the value of the product Business analyst's role Defining and determining value Function and use case points Agile estimating Planning Poker Other agile estimating techniques Negotiating estimates Negotiation techniques Negotiation approaches Summary What did we learn, and how can we implement this in our work environment?
Best Practices for Building Your Cross-Cultural Proficiency Join Christa Kirby for this presentation from IIL's International Project Management Day Online Conference discussing best practices for building your proficiency working with cross-cultural teams. This video covers best practices for leading both virtual and cross-cultural teams, touching on common pitfalls related to both. This and other IIL Learning in Minutes presentations qualify for PDUs. Some titles, such as Agile-related topics may qualify for other continuing education credits such as SEUs, or CEUs. Each professional development activity yields one PDU for one hour spent engaged in the activity. Some limitations apply and can be found in the Ways to Earn PDUs section that discusses PDU activities and associated policies. Fractions of PDUs may also be reported. The smallest increment of a PDU that can be reported is 0.25. This means that if you spent 15 minutes participating in a qualifying PDU activity, you may report 0.25 PDU. If you spend 30 minutes in a qualifying PDU activity, you may report 0.50 PDU.