2013-09-26

Seattle PMI-ACP Training
Event on 2013-10-09 08:30:00

PMI-ACP COURSE

This 3-day will help participants understand advanced techniques for product and iteration planning, project management and collaboration.  The agile project management approach is targeted at projects where fast responsiveness to changing market demands is important and for organizations with innovative cultures. An agile project management approach will help dramatically improve a project team’s ability to cope with change and will improve project success rate.

 

The course is designed for team managers, team members, product owners, Scrum coaches, XP coaches, project managers and technical managers who wish to become better team players and leaders. Using a combination of lectures, short exercises and role play as well as a long “agile experience”, the course introduces you to Agile practices and processes in the context of project management.

 

Upon successful completion of this course, you will receive a copy of the Scrum methodology, training materials, and software. In addition to completion of this course, participants are provided with 24 contact hours and/or PDU credits issued by the Project management research institute.

 

Objectives

By the end of this course, you will:

·         Understand Agile processes and practices

·         Understand Agile terminology such as Scrum, Sprint,

·         Be able to conduct various Scrum-oriented meetings such as Sprint Planning Meetings, Daily Standup Meetings, and Retrospective Meetings

·         Understand how to provide development estimates in the context of Scrums and Sprints

·         Be able to plan, run and scale Scrum projects

·         Know how to remove the barriers between development team and product owner/business representative or customer so that the latter drives development

·         Teach the customer how to maximize ROI and meet their objectives through Scrum

·         Improve effectiveness of the development team by facilitating creativity and empowerment

·         Improve the engineering practices and tools so each increment of functionality is potentially shippable

·         Understand the implications of offshore development using Scrum

·         Improve the adequacy of software engineering good practices

 Course Outline

 

8:30 AM – 9:00 AM (Breakfast & Networking)

9:00 AM – 6:00 PM (Training)

12:00 – 1:00 PM (Lunch Break & Interaction with Trainer)

10 minutes break will be provided by the trainer (if needed)

 

Day 1

 

8:30 AM – 9:00 AM (Breakfast & Networking)

 The Vision of Agile Project Management

·         Agile principles

·         Lean software development principles

·         The power of feedback

 

Understanding the key roles and artifacts of scrum 

Scrum master (Agile project manager)

Product owner

Team members

Product backlog

Sprint planning meeting

Sprint backlog

Tracking board

Sprint demo

Retrospectives

 

12:00 – 1:00 PM (Lunch Break & Interaction with Trainer)

 Agile Practices – an overview from management perspective

·         Identifying agile stakeholders and their roles

·         Focus on Scrum and ScrumMaster

·         Principles, practices, roles, challenges

 

Understanding user stories 

The anatomy of a user story

User story development techniques

Story points

Ideal time

Wide band delphi

Playing poker

 

 Agile Customer/Product Owner Practices

·         What product will we deliver

·         Product vision and product datasheet

·         Gathering requirements and building feature backlog

·         Writing and improving stories

·         Prioritizing features

·         Exploration spikes

·         Creating release plans

·         Iteration zero work

 

Day 2

 

8:30 AM – 9:00 AM (Breakfast & Networking)

 

10 minutes break will be provided by the trainer (if needed)

 Agile Development Practices

·         How do we approach the project

·         Deciding on good technical practices

·         Quality and Risk

·         Planning for collaboration, communication and decision making

 

The sprint planning meeting 

The sprint planning meeting time box

Feature prioritization

The tracking board

Definition of done

Load balancing

 

 Agile and Traditional Management

·         Traditional and agile planning – similarities

·         Agile projects and certification (CMM ea.)

 

 

12:00 – 1:00 PM (Lunch Break & Interaction with Trainer)

 

Sprinting 

Self organized teams

Work volunteering

Daily stand up meetings

Burn down chart updation

Sprint demo meetings Continuous improvement process

Velocity

Sprint retrospectives

Scaling scrum

Co-located and distributed teams

 Agile Estimation and Planning

·         Conducting daily meetings

·         Working with customers representatives

·         Sharing key project information

·         Release and Iteration Planning and Reporting

 

Best practices and concepts 

Agile tooling

Osmotic communications for co-located and distributed teams

WIP limits

Cumulative flow diagram

Process tailoring

Affinity estimating

Product road map

Story maps

Wire frames

Chartering

Frequent verification and validation

Test driven development / test first development

Continuous integration

Project charter for an agile project

Participatory decision models

Process analysis techniques

Self assessment

Value based assessment 

 

Day 3

 

8:30 AM – 9:00 AM (Breakfast & Networking)

 

10 minutes break will be provided by the trainer (if needed) The power of feedback — tracking progress and adapting

·         Running project retrospectives

·         Conducting technical reviews

·         Collecting and presenting project status information

·         Determining adaptation needs

 

Soft skills 

Negotiation

Emotional intelligence

Collaboration

Adaptive leadership

Conflict resolution

Servant leadership

Building high performance teams

 

Value based prioritization 

Return on investment (ROI)

Net present value (NPV)

Internal rate of return (IRR)

Compliance

Customer valued prioritization

Minimally marketable feature (MMF)

Relative prioritization / ranking

Business case development

 

12:00 – 1:00 PM (Lunch Break & Interaction with Trainer)

 

Agile implementation 

Agile contracting methods

Agile project accounting principles

Applying new agile practices

Compliance (Organization)

Control limits for agile projects

Failure modes and alternatives

Globalization, Culture and team diversity

Innovation games

Principles of systems thinking (complex, adaptive, chaoes)

Regulatory compliance

Variance and trend analysis

Vendor management

 Agile and large projects

·         Team work

·         Forming a team

·         Contributing to a team – preferences and strength

·         Peer-to-peer collaboration — Group-to-group collaboration

·         Running effective meetings

·         Communities of practice and tools for knowledge sharing

·         Leadership and empowerment

·         Dialogue

·         Learning organization

·         Change and Transition

at Postal code 10001, US

3333 E. University Drive

New York, United States

Seattle PMI-ACP Training is a post from: Nevada Sunshine

Show more