Imad Alsadeq, Qatar, May 2013 OPM3, MSP, PMP, PMOC, PMI-RMP, MCP

Similar documents
Agile Project Management By Mark C. Layton

How to manage agile development? Rose Pruyne Jack Reed

PLM - Agile. Design Code Test. Sprints 1, 2, 3, 4.. Define requirements, perform system design, develop and test the system. Updated Project Plan

Agile Practitioner: PMI-ACP and ScrumMaster Aligned

Agile Development Overview

Agile Overview. 30,000 perspective. Juha Salenius CSPO CSM PMI-ACP PMP SCGMIS Workshop January 23 rd, 2013

Issues in Internet Design and Development

Agile Project Management and Agile Practices Training; with a Scrum Project that you will do.

Agile Certification: PMI-ACP

Agile Project Management: Adapting project behaviors to the software development environment

Agile Scrum Training. Nice to meet you. Erik Philippus. Erik Philippus (1951)

Introduction to Agile and Scrum

Waterfall to Agile. DFI Case Study By Nick Van, PMP

ACP Exam Prep Plus Desk Reference including the Project Management Agile Body of Knowledge TM (PMABOK TM )

Agile Scrum Workshop

1. CMMI and Scrum TWO BRANCHES OF SOFTWARE DEVELOPMENT

10/4/2013. Sharif University of Technology. Session # 3. Contents. Systems Analysis and Design

Sometimes: 16 % Often: 13 % Always: 7 %

The Agile Manifesto is based on 12 principles:

Mike Cohn - background

Agile Processes and Distributed Projects: Dream or Nightmare?

Strategy. Agility. Delivery.

LEAN AGILE POCKET GUIDE

Agile Projects 7. Agile Project Management 21

Copyright protected. Use is for Single Users only via a VHP Approved License. For information and printed versions please see

Lean QA: The Agile Way. Chris Lawson, Quality Manager

AGILE SOFTWARE DEVELOPMENT: INTRODUCTION, CURRENT STATUS & FUTURE Pekka Abrahamsson Jyväskylä

Introduction to Agile Scrum

WE ARE FOCUSED ON HELPING OUR CLIENTS WORK SMARTER AND MORE EFFICIENTLY SO THAT TOGETHER, WE CAN EMPOWER PEOPLE TO DELIVER GREAT RESULTS.

AGILE & SCRUM. Revised 9/29/2015

Agile Development with Agile Business Suite

Scrum and Kanban 101

CHAPTER 3 : AGILE METHODOLOGIES. 3.3 Various Agile Software development methodologies. 3.4 Advantage and Disadvantage of Agile Methodology

Getting Agile with Scrum. Mike Cohn - background

SESSION 303 Wednesday, March 25, 3:00 PM - 4:00 PM Track: Support Center Optimization

AGILE - QUICK GUIDE AGILE - PRIMER

Agile Project Management

Agile Project Management

Agile Fundamentals, ROI and Engineering Best Practices. Rich Mironov Principal, Mironov Consulting

ITSM Agile Intro Feb 5, 2015

Development. Lecture 3

Digital Transformation of the Enterprise for SMAC: Can Scrum help?

Iteration Planning. also called Iteration Kickoff

The Basics of Scrum An introduction to the framework

Course Title: Planning and Managing Agile Projects

An Introduction to Scrum

Mitigating Risk with Agile Development. Rich Mironov CMO, Enthiosys

PMP vs. Scrum Master

Quality Assurance in an Agile Environment

Software Requirements and Specification

Course Title: Managing the Agile Product Development Life Cycle

Agile Beyond The Team 1

Getting Agile with Scrum

Scrum. SE Presentation. Anurag Dodeja Spring 2010

An Introduction to Scrum. The Agile Manifesto a statement of values

An Introduction to Agile Performance Management

USCIS/SPAS: Product Backlog Items and User Stories 4/16/2015. Dr. Patrick McConnell

Software Development Methodologies

Agile Software Development in the Large

Introduction to Agile

Overview of Scrum. Scrum Flow for one Sprint SCRUMstudy.com. All Rights Reserved. Daily Standup. Release Planning Schedule. Create.

What is Scrum? Scrum Roles. A lean approach to software development. A simple framework. A time-tested process

TSG Quick Reference Guide to Agile Development & Testing Enabling Successful Business Outcomes

Scrum. in five minutes

SECC Agile Foundation Certificate Examination Handbook

Getting Agile with Scrum. We re losing the relay race

Agile Information Management Development

Atern The latest version of the DSDM approach which makes DSDM appropriate to all types of project.

Agile Software Development. Stefan Balbo / Patrick Dolemieux

Agile Software Development

A Software Project Management Innovation (SPM) Methodology: A Novel Method for Agile Software Development

Processes in Software Development. Presented by Lars Yde, M.Sc., at Selected Topics in Software Development, DIKU spring semester 2008

Introduction to Agile and Scrum

The 2015 State of Scrum Report. How the world is successfully applying the most popular Agile approach to projects

Agile Project Management and the Real World. Emily Lynema DLF Fall 2010 November 1, 2010

Agile Project Management with Scrum

History of Agile Methods

Introduction to Agile Software Development Process. Software Development Life Cycles

Agile project management: A magic bullet?

A Viable Systems Engineering Approach. Presented by: Dick Carlson

Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012

Creating a High Maturity Agile Implementation

Why Agile Works: Economics, Psychology, and #PrDC16

Agile Training and Certification Options. David Hicks

Agile and Secure: OWASP AppSec Seattle Oct The OWASP Foundation

The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. July Developed and sustained by Ken Schwaber and Jeff Sutherland

CSSE 372 Software Project Management: More Agile Project Management

Secrets of a Scrum Master: Agile Practices for the Service Desk

Agile Software Development

Governments information technology

Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012

Comparative Study of Agile Methods and Their Comparison with Heavyweight Methods in Indian Organizations

D25-2. Agile and Scrum Introduction

Transcription:

Qatar, May 2013 Imad Alsadeq, OPM3, MSP, PMP, PMOC, PMI-RMP, MCP PMI is a registered trade and service mark of the Project Management Institute, Inc. 2013 Permission is granted to PMI for PMI Marketplace use only

EPMO Director, Ministry of Labor, KSA, Consultant, Trainer, Author, Translator, and Ireland 2011 Speaker. 2

Now and Here, Apply in your mind, As if you will explain today to your colleagues, Prepare your feedback through questions or e- mail. 3

Why Agile? What is Agile? Agile Manifesto Agile Methodologies How to Agile? Is it the right approach for us? Agile Tools

Projects success rate has not improved since 2000. To obtain better results, we suggest to use an approach that is radically different. What is the situation like in your organization? Chaos Report Standish Group, 2009 9

10

Project: Kodak s New Advantix Photographic system PMI recognized it as the 1997 International Project of the Year Business Week selected the system as one of the best new products of 1996 (Adams, 1998). After the Project Kodak's stock price has fallen 67% since the introduction of the Advantix system http://www.maxwideman.com/guests/metrics/abstract.htm

Project: Sydney Opera House Time Plan was 4 years Finished after 14 years Budget was 7M Actual cost about 102 After the Project One of the most recognized buildings in the world For the year ended 30 June 2011, total income was about 120M Adopted from: http://www.sydneyoperahouse.com

Project Management Success Project Success Stakeholders satisfaction Project outcome added value Project Success Competing Demands balancing Contribution to the Org. Strategy 13

14

http://www.versionone.com/ 15

http://www.versionone.com/ 16

19

Satisfy Customer Welcome Changing Shorter Timescale to deliver 2:8 Work Together Daily Trust Your Team Promote Sustainable Working Software Face-to-Face Conversation Good Design enhance agility Simplicity Self-organizing teams Retrospective 20

21

Iterative strategies for managing software development projects, such as Scrum, the Dynamic Systems Development Method (DSDM), Feature Driven Development (FDD ), the Agile Unified Process (AUP) and Lean Development Strategies for optimizing software development work, such as extreme Programming (XP) and the Rational Unified Process (RUP ) Strategies for managing software maintenance and support activities, such as Kanban. Cooke, 2012

http://www.versionone.com/ 23

24

Scrum is an Agile methodology for project management that involves: Delivering software in time-boxed iterations Focusing on the highest business-value software features in each iteration Interacting directly with business users to confirm ongoing software usability, quality, relevance and business value throughout the process. 25

"Servant-Leadership is a practical philosophy which supports people who choose to serve first, and then lead as a way of expanding service to individuals and institutions. Servantleadership encourages collaboration, trust, foresight, listening, and the ethical use of power and empowerment" Making sure your team's needs come first Allowing your team the freedom to do the best work they possibly can Fostering the personal growth of your team members Always acting in an ethical and caring manner Mentoring future servant leaders Robert Greenleaf, 2005

Scrum 31

Hours Tasks Code the user interface Mon 8 Tues Wed Thur Fri 4 8 Code the middle tier 16 12 10 7 Test the middle tier 8 16 16 11 8 Write online help 12 50 40 30 20 10 0 Mon Tue Wed Thu Fri

WHAT WENT WELL WHAT WENT LESS WELL SUGGESTIONS FOR IMPROVEMENT WHAT STILL PUZZLES US

Product owner Define the features of the product Decide on release date and content Be responsible for the profitability of the product (ROI) Prioritize features according to market value Adjust features and priority every iteration, as needed Accept or reject work results 34

The Scrum Master Represents management to the project Responsible for enacting Scrum values and practices Removes impediments Ensure that the team is fully functional and productive Enable close cooperation across all roles and functions Shield the team from external interferences 35

1. Tell: make decision as the manager 2. Sell: convince people about decision 3. Consult: get input from team before decision 4. Join: make decision together with team 5. Advise: influence decision made by the team 6. Confirm: ask feedback after decision by team 7. Delegate: no influence, let team work it out

The Scrum Team Typically 5-9 people Cross-functional: Programmers, testers, user experience designers, etc. Members should be fulltime May be exceptions (e.g., database administrator) Teams are self-organizing Ideally, no titles but rarely a possibility Membership should change only between sprints 37

Sweet spot in software product development Domains where market requirements change often Initiatives where requirements are unknown or unknowable Complex knowledge work Don t use agile if

Ensure that proper change management is in place Solicit buy-in and commitment at all levels Select the right project Run an inception Involve the right people Build the team Establish a Framework What a sprint/iteration looks like What other processes are used Produce a backlog Sprint/Iteration 0 Start building

Some used between 3-4 different tools A handful said they used as many as 15.

42

Requirement PMI Agile Certification Eligibility Requirements Description General Project Experience 2,000 hours working on project teams These hours must be earned within the last 5 years Active PMP or PgMP will satisfy this requirement Agile Project Experience Training in Agile Practices Examination 1500 hours working on agile project teams or with agile methodologies These hours are in addition to the 2,000 hours required in general project experience These hours must be earned within the last 3 years 21 contact hours Hours must be earned in agile practices Tests knowledge of agile fundamentals

Requirement PMI Agile Certification Eligibility Requirements Description General Project Experience 2,000 hours working on project teams These hours must be earned within the last 5 years Active PMP or PgMP will satisfy this requirement Agile Project Experience Training in Agile Practices Examination 1500 hours working on agile project teams or with agile methodologies These hours are in addition to the 2,000 hours required in general project experience These hours must be earned within the last 3 years 21 contact hours Hours must be earned in agile practices Tests knowledge of agile fundamentals

People are more motivated when they manage themselves. Teams and individuals are more productive when they are not interrupted. Productivity is compromised when changes are made to the team composition. Face-to-face communication is the most productive way for a team to work and exchange. 45

46

:) ialsadeq@gmail.com Find me at Drop me an e-mail Sponsored By: Imad Alsadeq OPM3, MSP, PMP, PMOC, PMI-RMP, MCP 47