Certified Scrum Product Owner (CSPO®)  Training
in Chennai, India

Key Features
  • 16 PDUS
  • 2 Days Classroom Training
  • Scrum Alliance approved Trainer (CST)
  • 100 Days Agile and Scrum E-learning access
  • Scrum Alliance Certification
  • 1 yr Membership with Scrum Alliance
Location
Country :
India
  
City: ( Change City )
Chennai
Date
Date: 
23rd - 24th Apr 2014
>> Click here to view other Certified Scrum Product Owner(CSPO®) locations in India
Course Price
INR 27000.00
Group Discount Available
Training Calendar
calender Click Here
calender Related Course Click Here calender Near Location Click Here

The Product Owner is the key member of the Scrum Team and shoulders the responsibility of leading the project strategically, collaborating with customers and team on a daily basis, and managing the business value. Though he doesn't need to be an expert in the process, the Product Owner must have sufficient understanding of the Agile Manifesto and enough knowledge to assist the ScrumMaster if the need arose.

Our two-day Certified Scrum Product Owner Course is delivered by Scrum Alliance Certified Trainers (CSTs) and offers blended-learning combining classroom study, group discussions, and hands-on practice exercises, to give you a keen understanding of Scrum from the point of view of a Product Owner, enabling you to be an effective customer to the Scrum team and maximizing ROI.

Course Agenda of Satisha Venkataramaiah CST (23rd - 24th Apr 2014)

We will be learning the Product Ownership using Scrum. The whole course is split inot 4 Sprints with each Sprint trying to Answer following four questions:

  1. Why are we building Products?
  2. What are we building?
  3. How much do we build?
  4. How do we build?

Sprint 1: Why are we building Products?

Agile Values and Principles

  • Understanding Empiricism.
  • Introduction to Agile Manifesto
  • 12 Agile Principles

Scrum Framework

  • Introduction to Scrum Framework
  • Scrum Roles
  • Scrum Artifacts
  • Scrum Ceremonies
  • Understading the role of Product Owner

    • Who is a Product Owner?
    • What are the attributes of a good Product Owner
    • What are the responsibilities of a Product Onwe.

    Sprint 2: What are we building?

    Product Visioning

    • What's a Product Vision?
    • Developing a Product Vision.
    • Where do we start? Business Canvas, Lean Canvas and Product Canvas.
    • Choose a Product to work on and develop a Produt Vision for the Product

    Impact Mapping

    • What is impact mapping?
    • How impact map helps in delivering Products that matter
    • Developing initial impact map for the class Product
    • Grooming Product Backlog

    Identifying Users and Personas

    • Understanding Actors for the Product
    • What's a Persona and Identifying personas for the class Project

    Building a Product Backlog

    • Characteristics of a Product Backlog
    • What are user stories?
    • What's a Story Workshop/Backlog refinement?
    • How to split large stories into approproiate size?
    • Build backlog for the class project

    Sprint 3: How much do we build?

    Prioritization

    • Impact based Prioriitization: Impact map continued
    • Understadning User sentiments for Prioritization: Kano Analysis
    • Building a Skeleton that a user can use: User Story Mapping
    • Assigning business value to Stories – Business Value Game
    • Prioritization based on Technical Risk
    • Prioritize the product backlog for class project

    Estimation

    • What is estimation?
    • How do we measure the delivery?
    • What techniques can be used for estimation?

    Release Planning

    • When do we release? Understanding the value of shortening the feedback loop through early and incremental releases
    • What's Lean Statrup? Applying the Lean Startup concepts while building products using Scrum
    • Fake it until you know it: Uncovering user preferences without building features
    • What factors drive release decision?
    • Collaborating with customers to make a release decision
    • How do we arrive at a release date?
    • Why release plan is not cast in stone and release planing should be iterative?

    Sprint 4: How do we build?

    Sprint Planning

    • What's the role of PO in Sprint Planning?
    • Collaborating with Development Team to deliver the impactful stories first

    Being Ready to Release

    • What's Definition of Done?
    • What's Technical Debt and how to avoid it to deliver useable products
    • How Engineering Practices help produce quality product

    Are we there yet?

    • What do we measure to understand that we are making the right impacts?
    • Getting customer feedback
    • Measuring progress based on Customer feedback
    • What's velocity? How does it help to plan releases

    Course Agenda of Satisha Venkataramaiah CST (29th - 30th Apr 2014)

    We will be learning the Product Ownership using Scrum. The whole course is split inot 4 Sprints with each Sprint trying to Answer following four questions:

    1. Why are we building Products?
    2. What are we building?
    3. How much do we build?
    4. How do we build?

    Sprint 1: Why are we building Products?

    Agile Values and Principles

    • Understanding Empiricism.
    • Introduction to Agile Manifesto
    • 12 Agile Principles

    Scrum Framework

  • Introduction to Scrum Framework
  • Scrum Roles
  • Scrum Artifacts
  • Scrum Ceremonies
  • Understading the role of Product Owner

    • Who is a Product Owner?
    • What are the attributes of a good Product Owner
    • What are the responsibilities of a Product Onwe.

    Sprint 2: What are we building?

    Product Visioning

    • What's a Product Vision?
    • Developing a Product Vision.
    • Where do we start? Business Canvas, Lean Canvas and Product Canvas.
    • Choose a Product to work on and develop a Produt Vision for the Product

    Impact Mapping

    • What is impact mapping?
    • How impact map helps in delivering Products that matter
    • Developing initial impact map for the class Product
    • Grooming Product Backlog

    Identifying Users and Personas

    • Understanding Actors for the Product
    • What's a Persona and Identifying personas for the class Project

    Building a Product Backlog

    • Characteristics of a Product Backlog
    • What are user stories?
    • What's a Story Workshop/Backlog refinement?
    • How to split large stories into approproiate size?
    • Build backlog for the class project

    Sprint 3: How much do we build?

    Prioritization

    • Impact based Prioriitization: Impact map continued
    • Understadning User sentiments for Prioritization: Kano Analysis
    • Building a Skeleton that a user can use: User Story Mapping
    • Assigning business value to Stories – Business Value Game
    • Prioritization based on Technical Risk
    • Prioritize the product backlog for class project

    Estimation

    • What is estimation?
    • How do we measure the delivery?
    • What techniques can be used for estimation?

    Release Planning

    • When do we release? Understanding the value of shortening the feedback loop through early and incremental releases
    • What's Lean Statrup? Applying the Lean Startup concepts while building products using Scrum
    • Fake it until you know it: Uncovering user preferences without building features
    • What factors drive release decision?
    • Collaborating with customers to make a release decision
    • How do we arrive at a release date?
    • Why release plan is not cast in stone and release planing should be iterative?

    Sprint 4: How do we build?

    Sprint Planning

    • What's the role of PO in Sprint Planning?
    • Collaborating with Development Team to deliver the impactful stories first

    Being Ready to Release

    • What's Definition of Done?
    • What's Technical Debt and how to avoid it to deliver useable products
    • How Engineering Practices help produce quality product

    Are we there yet?

    • What do we measure to understand that we are making the right impacts?
    • Getting customer feedback
    • Measuring progress based on Customer feedback
    • What's velocity? How does it help to plan releases

    Course Agenda of Satisha Venkataramaiah CST (07th - 08th May 2014)

    We will be learning the Product Ownership using Scrum. The whole course is split inot 4 Sprints with each Sprint trying to Answer following four questions:

    1. Why are we building Products?
    2. What are we building?
    3. How much do we build?
    4. How do we build?

    Sprint 1: Why are we building Products?

    Agile Values and Principles

    • Understanding Empiricism.
    • Introduction to Agile Manifesto
    • 12 Agile Principles

    Scrum Framework

  • Introduction to Scrum Framework
  • Scrum Roles
  • Scrum Artifacts
  • Scrum Ceremonies
  • Understading the role of Product Owner

    • Who is a Product Owner?
    • What are the attributes of a good Product Owner
    • What are the responsibilities of a Product Onwe.

    Sprint 2: What are we building?

    Product Visioning

    • What's a Product Vision?
    • Developing a Product Vision.
    • Where do we start? Business Canvas, Lean Canvas and Product Canvas.
    • Choose a Product to work on and develop a Produt Vision for the Product

    Impact Mapping

    • What is impact mapping?
    • How impact map helps in delivering Products that matter
    • Developing initial impact map for the class Product
    • Grooming Product Backlog

    Identifying Users and Personas

    • Understanding Actors for the Product
    • What's a Persona and Identifying personas for the class Project

    Building a Product Backlog

    • Characteristics of a Product Backlog
    • What are user stories?
    • What's a Story Workshop/Backlog refinement?
    • How to split large stories into approproiate size?
    • Build backlog for the class project

    Sprint 3: How much do we build?

    Prioritization

    • Impact based Prioriitization: Impact map continued
    • Understadning User sentiments for Prioritization: Kano Analysis
    • Building a Skeleton that a user can use: User Story Mapping
    • Assigning business value to Stories – Business Value Game
    • Prioritization based on Technical Risk
    • Prioritize the product backlog for class project

    Estimation

    • What is estimation?
    • How do we measure the delivery?
    • What techniques can be used for estimation?

    Release Planning

    • When do we release? Understanding the value of shortening the feedback loop through early and incremental releases
    • What's Lean Statrup? Applying the Lean Startup concepts while building products using Scrum
    • Fake it until you know it: Uncovering user preferences without building features
    • What factors drive release decision?
    • Collaborating with customers to make a release decision
    • How do we arrive at a release date?
    • Why release plan is not cast in stone and release planing should be iterative?

    Sprint 4: How do we build?

    Sprint Planning

    • What's the role of PO in Sprint Planning?
    • Collaborating with Development Team to deliver the impactful stories first

    Being Ready to Release

    • What's Definition of Done?
    • What's Technical Debt and how to avoid it to deliver useable products
    • How Engineering Practices help produce quality product

    Are we there yet?

    • What do we measure to understand that we are making the right impacts?
    • Getting customer feedback
    • Measuring progress based on Customer feedback
    • What's velocity? How does it help to plan releases

    Course Agenda of Heitor Roriz Filho CST (01st - 02nd Jul 2014)

    Scrum Concepts: Basics of Scrum Framework , Principles and Values ​​to ensure the proper understanding and implementation of Scrum .

    Scrum theory : The three pillars of Scrum ( inspection, transparency and adaptation ) are explained and the resulting and values ​​are examined in details : responsibility, self - organization and self- management, sense of urgency , commitment , technical excellence , rhythm , discipline, respect and courage .

    The Scrum Framework : meetings , artifacts and roles that make up the Scrum process .

    Principles of Agile Project Management : The Role of PO in project management , focus on customer needs , techniques for aligning the vision, understanding and analyzing the initial requirements , the definition of ROI and business value , techniques for quantifying business value and ROI , business proposals , contract theory in Agile .

    Estimates and Planning :The Five Levels of estimates and planning concepts , think of different levels of abstraction , the Scrum framework from the point of view of a Product Owner , the tasks performed before a project , the tasks of the OP during and after a sprint , the construction of the Product Backlog , the Dynamics of Product Backlog prioritization techniques , planning poker and writing user stories .

    Planning and Managing a Release : The importance of minimally essential planning , technical meetings for release planning , release planning poker in planning , writing workshop stories , agile metrics tracking releases, burn-up charts and burndown .

    Product Backlog Grooming : useful for the alignment of Scrum and organizational needs ( metrics , reports , etc ) using the Product Backlog , Definition of Ready , PO ceremony in Backlog Refinement Tips .

    Evolution of Scrum : Defining Distributed Scrum , Scrum of Scrums , Product Owner Settings , Scrum beyond software , Scrum and pre - defined processes like PMBOK , CMMI .

    Other topics as demanded by participants , within the time available .

    Course Agenda of Heitor Roriz Filho CST (06th - 07th Jul 2014)

    Scrum Concepts: Basics of Scrum Framework , Principles and Values ​​to ensure the proper understanding and implementation of Scrum .

    Scrum theory : The three pillars of Scrum ( inspection, transparency and adaptation ) are explained and the resulting and values ​​are examined in details : responsibility, self - organization and self- management, sense of urgency , commitment , technical excellence , rhythm , discipline, respect and courage .

    The Scrum Framework : meetings , artifacts and roles that make up the Scrum process .

    Principles of Agile Project Management : The Role of PO in project management , focus on customer needs , techniques for aligning the vision, understanding and analyzing the initial requirements , the definition of ROI and business value , techniques for quantifying business value and ROI , business proposals , contract theory in Agile .

    Estimates and Planning :The Five Levels of estimates and planning concepts , think of different levels of abstraction , the Scrum framework from the point of view of a Product Owner , the tasks performed before a project , the tasks of the OP during and after a sprint , the construction of the Product Backlog , the Dynamics of Product Backlog prioritization techniques , planning poker and writing user stories .

    Planning and Managing a Release : The importance of minimally essential planning , technical meetings for release planning , release planning poker in planning , writing workshop stories , agile metrics tracking releases, burn-up charts and burndown .

    Product Backlog Grooming : useful for the alignment of Scrum and organizational needs ( metrics , reports , etc ) using the Product Backlog , Definition of Ready , PO ceremony in Backlog Refinement Tips .

    Evolution of Scrum : Defining Distributed Scrum , Scrum of Scrums , Product Owner Settings , Scrum beyond software , Scrum and pre - defined processes like PMBOK , CMMI .

    Other topics as demanded by participants , within the time available .

    From the course:

    • Boost Product Owner capabilities
    • Optimize Agile teams as well as interaction with stakeholders and customers
    • Increase Scrum functionality
    • Realistic planning and scheduling
    • Gain practical, proven techniques
    • Improve estimating skills and results
    • Maximize delivery capabilities
    • Reduce risk
    • Improve ROI
    • Leverage proven experience

    From the workshop:

    • Training by experienced Scrum Alliance Certified Instructors (CSTs)
    • 14 – 16 PDUs (Varies according to CST)
    • Scrum Alliance Certification
    • 1 yr Membership with Scrum Alliance
    • Scrum Alliance-approved Courseware
    • Hands-on Activities, Group Discussions, Real-life examples.

    Eligibility:

    Your successful completion of the 2-day CSPO course provided by our Certified Scrum Trainer makes you eligible for the CSPO Certification from Scrum Alliance.

    Process:

    There is no process. Following successful completion of this course, you will receive a Certificate from Scrum Alliance designating you as Certified Scrum Product Owner. The certification includes a one-year membership in Scrum Alliance.

    This training and certification is ideal for

    • Project Managers
    • Developers
    • Product Owners
    • Managers-Software development
    • Architects-Software development
    • Product Managers
    • Software developers
    • Software coders
    • Software testers
    • Team Leads or Team Members who are interested in learning more about Scrum and leading Agile projects.

    What does it mean to be a CSPO?

    A Certified Scrum Product Owner (CSPO) is someone who has been taught (by a Certified Scrum Trainer) the Scrum terminology, practices, and principles that will enable him or her to fulfill the role of Scrum product owner.

    Do I receive PDU credits for a CSPO course?

    Yes. Please follow PMI''s procedure for Category B: Courses offered by Other Education Provider. According to the PMP handbook: 'Contact hours of project and/or program management education may be earned by attending relevant educational courses offered by organizations not registered with PMI. To calculate the number of PDUs earned, use the following formula: one contact hour of learning relevant to project and/or program management within a structured activity or course equals one PDU. Documentation required upon PMI audit/request: registration form, certificate or letter of attendance, and a brochure or course materials outlining the subject matter covered and the qualifications of the instructor/lecturer.' Most CSTs can tell you how many PDUs their course offers.

    Should I do both Certified ScrumMaster and Certified Scrum Product Owner if I don't know where I will be working?

    Both designations address different concerns for developing Products. Employers are looking for people with a background in agile (scrum). These designations will help identify you as having been trained in Scrum. Experience still counts so time spent doing Scrum is equally valuable.

    In Scrum, which person is the Project Manager? Is it the ScrumMaster or the Scrum Product Owner?

    The short answer is neither. The term Project Manager is not defined in Scrum. The term Project Manager is defined broadly in the market and is used differently by many organizations. If you compare the terms side by side you will find that sometimes it is the PO, sometimes the SM and sometimes it is both. Again, the term is not defined in Scrum but, you can compare them.

    Which should I pursue: Certified ScrumMaster (CSM) or Certified Scrum Product Owner (CSPO)? Why?

    Both certifications will lead to a full understanding of Scrum. The CSPO is targeted for Product Owners who need skills and techniques for managing features and determining what the right product to build is. The CSM is a deep dive introduction to Scrum. CSM is focused on the scrum framework and its application for building well form teams that are directed by a Product Owner. The CSM is recommended for all Scrum team members, this include Product Owners.

    Would it be better to spend time renewing a PMP credential or becoming a Certified ScrumMaster or Product Owner?

    Becoming a CSM and/or CSPO is recommended. We are seeing increase demand from companies who are looking for people with CSM / CSPO experience.

    I understand Scrum is used widely for software development projects. Can it be used for other fields?

    Scrum has seen an application into every major vertical industry. The number of domains outside software that it has been applied to is increasing rapidly. Scrum is a general purpose framework that is used to set an empirical pattern of behavior at a small team level. Scaling Scrum is thought of as multiple scrum teams working together in an empirical process controlled manner.

    How do I get my certificate and who issues it?

    Students taking classes offering a Scrum certification (Certified ScrumMaster and Certified Product Owner) will receive their certifications from the Scrum Alliance. Shortly after completion of the class, participants will receive an email from the Scrum Alliance with instructions for creating a membership account and taking any required certification exams. Once certified, students will have access to exclusive content and the ability to print a copy of any Scrum certificates they have achieved.

    What time do classes start and how long do they go each day?

    Unless otherwise stated, all of our classes begin at 8:30 and run to 5:00 PM, local time. Classes generally include a break for lunch around noon, as well as a brief break in the morning and afternoon.

    What are the benefits of taking a class to learn about Agile & Scrum as opposed to simply reading a book?

    Books are valuable resources and we strongly encourage potential students to leverage these sources of information. Our training classes are designed to reinforce concepts with in depth simulations and robust discussion. All of our course blend lecture, practice, and reflection. This allows participants to gain a much more profound understanding of the subject matter.

    What do I need to bring to a class?

    Our classes are designed to be a stand-alone experience and do not require participants to bring anything to a class other than an open mind and willingness to learn and perhaps something to take notes.

    Can I buy a seat with a Purchase Order?

    Yes, we will accept purchase orders. Please email us at support@knowledgehut.com to arrange for payment via a purchase order.

    What happens if a class is canceled?

    In the case that a class is canceled by KnowledgeHut, participants are entitled to transfer to another class or receive a full refund at their discretion.

    What does it mean to be a Certified Scrum Professional (CSP)?

    A Certified Scrum Professional has proven experience and expertise in the art of Scrum. CSP is the level of certification that all practitioners of Scrum should strive to attain. Before becoming a CSP, applicants must be CSMs, CSPOs, or CSDs.

    Faculty for Chennai (23rd - 24th Apr 2014)

    Satisha Venkataramaiah CST

    Satisha Venkataramaiah CST

    I'm a strong believer of the fact that human beings are born with a trait to inspect and adapt. Human beings collaborate well in small herds. So I believe that any activity (software development, coaching or training) is highly effective when worked with smaller teams, hands on than taking on an enterprise. I had privilege to sit next to customer and develop software to solve their problems 30 minutes into my first job. So I strongly believe in collaborating with customer's to build simple and valuable products rather than building sophisticated fancy products.

    I have over 15 years of experience in developing software in various roles such as a Programmer, Release Engineer, Analyst, Project Manager, Scrum Master, Product Owner and Agile Coach but every role focused on the value being created for the end user.

    I also believe that the learning never ends so I co-learn by facilitating the following workshops

    • Agile Foundations
    • Software Development using Scrum
    • Advanced Skills for Scrum Master
    • Agile Planning and Estimation
    • Agile Project Management using JIRA+GreenHopper
    • Collaboration Tools for Agile [GreenHopper, JIRA, Jenkins, Crcible, FishEye etc]
    • Software Configuration Management for Agile Teams

    Venue for Chennai - 23rd - 24th Apr 2014

    Radha Regent
    171, Jawaharlal Nehru Salai(Inner Ring Road), Arumbakkum
    Chennai, Tamilnadu 600106 India

    Timing: 8:30AM to 5:30PM