 Agile Project Management, Collaboration Tool-Sets & PPM Tool-Sets Presented by Tayo Akingboye PMP, PMI-ACP.

Slides:



Advertisements
Similar presentations
Management, Leadership, & Internal Organization………..
Advertisements

Life Science Services and Solutions
AGILE DEVELOPMENT Outlines : Quick Look of agile development Agility
SDLC – Beyond the Waterfall
COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. 1 Agile documentation development methodology Giby Panicker and Judith Benjamin 1-Dec-2012.
PROC-1 3. Software Process. PROC-2 What’s a process? Set of activities in creating software It involves creativity –hard to automate –Requires human judgment.
Agile and Scrum: Executive Summary June 2, 2011 Bob Schommer, CSP, PMP, MCTS Senior Project Manager Skyline Technologies, Inc.
Agile Project Management with Scrum
Agile development By Sam Chamberlain. First a bit of history..
1 Agile Methodologies in DoD Software By Cynthia Johnson.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
The Challenge to Survive in Today’s Software Development Environment Evaluating the Agile Methodology.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
COMP 350: Object Oriented Analysis and Design Lecture 2
CHAPTER 9: LEARNING OUTCOMES
Managing a Project Using an Agile Approach and the PMBOK® Guide
User training and driving adoption PPM system configuration to “meet” with the methodology Choose between on- premises or online PPM methodology implementation.
Agile Process: Overview n Agile software engineering represents a reasonable compromise to conventional software engineering for certain classes of software.
An Agile View of Process
Introduction to Agile.
Software engineering Process models Pavel Agejkin.
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
1 Agile Methodology & Programming Ric Holt July 2009.
Chapter 4 Agile Development
Chapter 4 Agile Development 1. The Manifesto for Agile Software Development 2 “We are uncovering better ways of developing software by doing it and helping.
Tuesday, June 8 th, Agile Development-Successful Delivery & Implementing Across the Enterprise.
Current Trends in Systems Develpment
AgileCamp Presents: Agile 101. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons Attribution.
1 The Manifesto for Agile Software Development “We are uncovering better ways of developing software by doing it and helping others do it. Through this.
K.Ingram 1 Sept 2007 Agile Software Development. K.Ingram 2 Sept 2007 Contents Agile Software Development: 1.What is it? 2.Agile’s Values, Principles,
© 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v
Agile Methodology Paul Mohrbacher. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through.
Agile Software Development By Kshitij Limaye CSC 532.
Theories of Agile, Fails of Security Daniel Liber CyberArk.
Software Engineering (CSI 321) An Agile View of Process 1.
#AgileEd. Using Agile in the Classroom Cindy Royal, Associate Professor Texas State University slideshare.net/cindyroyal #AgileEd.
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
10 key principles of agile software development
Module 2: What is Agile? Why use it? TLO: Given a DoD program involved in software development, the student will recognize situations where applying agile.
Using Scrum to Improve Teamwork, Communication, Quality and Speed
CS223: Software Engineering Lecture 16: The Agile Methodology.
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
Extreme Programming מתודולוגיה לפיתוח פרויקטי תוכנה.
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Embedded Systems Software Engineering
Chapter 5 Agile Development Moonzoo Kim KAIST
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
AGILE SCRUM METHODOLOGY
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Waterfall, Agile & Scaling Agile
Digital Workplace.
Agile Software Development
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Agile Software Development Brian Moseley.
Information Technology Project Management – Fifth Edition
Chapter 3: The Project Management Process Groups: A Case Study
COMP 350: Object Oriented Analysis and Design Lecture 2
Tim Hirner - Flagship Speakers January 23, 2014
How to Successfully Implement an Agile Project
Agile Process: Overview
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Introduction to Agile Blue Ocean Workshops.
Adjective: Able to move quickly and easily. Principles and Values
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Scrum Science NGSS: Engineering, Technology, Applications of Science
Project Lifecycle and IT Product Life Cycle
Topic 1: Introduction to the Module and an Overview of Agile
Presentation transcript:

 Agile Project Management, Collaboration Tool-Sets & PPM Tool-Sets Presented by Tayo Akingboye PMP, PMI-ACP

Presentation Outline  Agile Project Management  Brief History  Definition: Agile Project Management  Phases in Agile Project Management  Collaboration Tool-Sets  Definition  Factors that affect selection  Comparison of collaboration tools  PPM Tool-sets  Definition: Project Portfolio Management  Main Contenders in PPM Tool-Sets  Key Features of PPM Tool-Sets  Making PPM a Business Process  Conclusion  Linking all concepts together

Brief History Agile Project Management is based on the Agile Manifesto which was created within Feb 11-13, 2001 by 17 independent-minded software practitioners in Snobird, Utah. Agile was created as an alternative to documentation driven, heavy-weight software development. Agile Manifesto: This is a public declaration of the principles and philosophy of Agile Project Management.  Individuals and Interactions over Processes and Tools  Working Software over comprehensive documentation  Customer collaboration over contract negotiation  Responding to change over following a plan While there is value in the items on the right, the items on the left are more valued.

Agile Project Management is a change driven approach in that it refers to the iterative, incremental method of managing project design, analysis and implementation in order to create a new product, service in a highly flexible and interactive manner. There are several forms of Agile Project Management such as SCRUM, CRYSTAL, XP (Extreme Programming), DSDM (Dynamic Software Development Methodology), FDD (Feature Driven Development). Agile Project Management places high emphasis on Progressive Elaboration/Rolling Wave planning. There are 3 Key artifacts used in Agile which are Project Vision, Product Road-Map and Backlogs (Product Backlog & Release Backlog). Key meetings/ceremonies that occur in Agile Project Methodology are: Daily Stand-ups, Sprint Planning, Sprint Review, Sprint Retrospective Definition: Agile Project Management

Phases in Agile Project Management

Benefits of Agile Project Methodology  Higher Productivity and Lower Costs  Improved employee engagement and job satisfaction  Faster Time-To-Market  Higher Quality  Improved stakeholder satisfaction

Definition: Collaboration Collaboration can be defined as "an intense commingling of ideas and inspiration shared by two or more people seeking to find solutions to specific challenges and goals that are innovative, practical and achievable within the framework of the organization/communities they serve.“ Collaboration tool-sets enhance collaboration and these tools can either be non-technological like whiteboards, Kanban Boards, Post-it notes etc or purely technology based like Google Apps, DropBox, Asana etc.

Team Size and working style: select collaboration tools that can adequately support the size of the project team, multiple forms of collaboration and lastly different file types. Ability to integrate with other tools: ensure that the collaboration tool can integrate with other tools to ensure seamless information flow. The ability to integrate with document sharing apps like Google Drive, DropBox or social media, calendars/ gantt charts empowers your team to ensure purposeful collaboration. Real-time collaboration: allows a team to edit, work together on multiple files, present feedback, leave comments and chat with others in real time. In this situation, management of files (File version, who can edit/share files, timestamps) and users (who can contribute to discussion, edit files) is really important. Hosting On-Premise vs In the Cloud: speed of software deployment, pricing model, IT organizational capacity and provision of operational support are key aspects that affect which collaboration tool to adopt. Free/Trial Version: the ability to test drive a trial version to inspect easy of use, performance and overall simplicity is also important in software evaluation. Factors that affect selection

Comparison of Collaboration Tool-Sets

Comparison of Collaboration Tool-Sets continued

Project Portfolio management can be described as the set of processes, supported by people and tools, to guide the enterprise in selecting the right projects and the right number of projects, and in maintaining a portfolio of projects that will maximize the enterprise's strategic goals, efficient use of resources, stakeholder satisfaction, and the bottom line. Definition: Project Portfolio Management

Main Contenders in PPM Tool-Sets

Comparison continued…

Pipeline Management: Sometimes called pipeline assessment and analysis, this feature helps managers determine whether a project or a set of projects can be finished with the time and resources on hand. Resource Distribution: efficiently allocate company resources to projects as needed, this feature allows you to manage and distribute financial, inventory, technical, and human resources. Change Management: PPM software provides a central repository for various change requests. This allows you to quickly assess inquiries as they arise, and match available resources to overall demand. Financial Administration: ability to provide the anticipated financial value of projects in relation to strategic objectives and organizational priorities.If you are able to determine when projects will fall short of financial expectations, you can change the parameters or cease investment before incurring losses. Risk Management: allows you to analyze the risk present in each existing and potential project to determine confidence levels across the portfolio. By grouping projects together, you can evaluate confidence levels on a categorical basis, and assist financial and resource allocation decisions Key Features of PPM Tool-Sets

How to make PPM a Business Process Align leadership: Implementing PPM as a business process is a game changer and requires adequate change leadership. Part of that is executive alignment. A key element of the alignment process is visualization. Senior leaders must be able to envision what the future- state looks and how that improves their business area and the organization as a whole. Implement and deploy: PPM is an enterprise application, which means that the implementation and deployment must be managed as such. The focus of the implementation must be on business process, analytics, application and governance. Execute, learn and adjust: When the PPM solution goes live, it’s the start of a new beginning. The primary focus of the project team and business must be on user adoption and tying the experience back to the original business case.

Conclusion: Linking Agile, Collaboration and PPM Agile Project Methodology High emphasis on maximizing value Team management can be gauged by levels of communication and collaboration PPM Evaluating projects that align with organizational objectives Portfolio management through effective resource management Collaboration Agile requires higher stakeholder engagement and collaboration Team collaboration is essential to successful project management

References Agile Concepts New Agile Process Diagram.pdf by RMC Collaboration Concepts PPM Concepts PPM and Agile: Realizing Best of Both Worlds process.html process.html