Valuable Project Management Tools and Techniques

Slides:



Advertisements
Similar presentations
Basic SDLC Models.
Advertisements

Unified process(UP) UP is an OO system development methodology offered by Rational(Rational Rose) s/w, now a part of IBM Developed by Booach,Rambaugh,Jacobson--
Agile Software Development کاری از : مهدی هوشان استاد راهنما : استاد آدابی.
AGILE DEVELOPMENT Outlines : Quick Look of agile development Agility
SOFTWARE DEVELOPMENT METHODOLOGIES Methodologies Waterfall Prototype model Incremental Iterative V-Model Spiral Scrum Cleanroom RAD DSDM RUP.
SDLC – Beyond the Waterfall
Software Development Life-Cycle Models
Software development process improvement Ville Wettenhovi Master thesis presentation Supervisor:Professor Jukka Manner Instructor:M.Sc. Markus Aalto Date:23th.
Sharif University of Technology Session # 3.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
Agile development By Sam Chamberlain. First a bit of history..
Software Life Cycles ECE 417/617: Elements of Software Engineering
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions.
Agile Process: Overview n Agile software engineering represents a reasonable compromise to conventional software engineering for certain classes of software.
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.
Software Development Life Cycle (SDLC)
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
CPSC 371 John D. McGregor Session 22 Process. Specification and design problem solution specification implementation specification.
Building a new HMS from scratch Bite size software delivery Richard Troote Alex Stephenson Head of ICT Head of Property Services.
Chapter 2 Software processes. Topics covered Software process models Process activities Coping with change.
The Confounding World of Process Methodologies By Thelma Hataria.
Software Development Overview CPSC 315 – Programming Studio Spring 2013.
© 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v
Department of Industrial Engineering Sharif University of Technology Session #8.
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
It’s Agile …. like! A Corkman’s introduction to Agile software delivery.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Extreme programming (XP) Advanced Software Engineering Dr Nuha El-Khalili.
AGILE SOFTWARE DEVELOPMENT. Agile software development : Agile software development refers to a group of software development methodologies that promotes.
Presented By : Prima Business Solutions. Agile Software Development Process.
Agile Gintarė Bernotaitytė © 2013.
Project Management Software development models & methodologies
Chapter 3 Agile software development 1 Chapter 3 – Agile Software Development.
Software Engineering cosc 4359 Spring 2017.
CS223: Software Engineering
Agile Project Management and the yin & yang of
Agile Methodology and Scrum
Agile Project Management Athanasios Podaras
Agile Training for Students
AGILE SCRUM METHODOLOGY
Flight Software Conference 2016
Introduction to Agile Software Development
Methodologies and Algorithms
Appendix B Agile Methodologies
Ernest Cachia Department of Computer Information Systems
Software Development methodologies
Iterative and Agile Development
Agile Software Development Brian Moseley.
Information Technology Project Management – Fifth Edition
Chapter 2: The Project Management and Information Technology Context
Software Engineering (CSI 321)
Rapid software development
Introduction to Software Engineering
Tim Hirner - Flagship Speakers January 23, 2014
Software Development Process
Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger Joanne M. Atlee 4th Edition.
Lecture 2 Revision of Models of a Software Process
Agile Process: Overview
System DEVELOPMENT LIFE CYCLE MODELS
Chapter 3 – Agile Software Development
Software Development methodologies
Project Lifecycle and IT Product Life Cycle
The New Methodology Martin Fowler Paper Presented by Vyshali Belagodu
Agile Development.
Chapter 5: New and Emerging Process Methodologies
System Development Methods
Software Development Process
International Institute of Business Analysis
Presented by: Dishant Mittal CS 846
Presentation transcript:

Valuable Project Management Tools and Techniques Why I Do What I Do the Way I Do It – an Introduction to the Mind of Shannon Shannon Bradley – September 1, 2017

Techniques No Project Manager Should Do Without Quality Communication It has to be regular Actions speak louder than words - and in business repeated actions are what shape our reputation Regular communication should relay both good and bad news With bad news – the earlier the better Twice is best – First when you know there is an issue and second when you know the details Confirm preferred individual communication preference at the beginning of the project Phone, Email, Chat, or In-Person Beginning and Ending Project Summaries are important Project Charter/Scope – so there is no question about what is being delivered Closing Documents – so project completion is verified and it can be referenced in the future Documented Changes should not be optional

Shannon’s View on Agile Project Management Provide new development in a highly flexible and interactive manner Requires capable individuals from the relevant involved parties, openness to consistent customer input throughout the process, and openness to non- hierarchical forms of leadership Designed to avoid various obstacles that develop in more sequential forms of project organization Method can be Fully agile where team completes small portions of the project deliverables in each delivery cycle; some can be completed before the end of project Or iterative where team progresses on the entire set of deliverables over time; completing them near the end of the project Unlike Waterfall where a stage must finish before the next can begin End result is a project that best meets current customer needs and is delivered with minimal costs, waste, and time, enabling companies to successfully complete a project earlier than via traditional approaches https://en.wikipedia.org/wiki/Agile_management

Scrum Think of it as a framework for managing processes surrounding a project Scrum relies on a self-organizing, cross-functional team there is no overall team leader who decides which person will do which task or how a problem will be solved issues are decided by the team as a whole each person contributes in whatever way they can to complete the work of each sprint Scrum processes define a specific method for planning, updates, reviewing and feedback that allows for deliverables to be completed during each project timeframe subset This allows the team to have incremental delivery of features or segments of the project which allows speedy utilization rather than a big release in the future when everything is completed Immediate gratification rather than realizing all value at the end https://www.mountaingoatsoftware.com/agile/scrum

Agile Methodologies “All Over the Place” in Addition to Scrum Adaptive software development (ASD) Agile modeling Agile Unified Process (AUP) Crystal Clear methods Disciplined agile delivery Dynamic systems development method (DSDM) Extreme programming (XP) Feature-driven development (FDD) Lean software development RAD (Rapid Application Development)

What Programmers Like? At the core a programmer dislikes and distrusts micromanagement. They are the best person to know their own capabilities and what is best to work on during a particular programming day or time frame. Micromanagement of a programmer leads to lack of ownership and lack of vesting in the success of a project and you basically turn them into a Code Monkey instead of a Developer. The most typical cause of failed agile implementations is insufficient training. Teams assume that there are no real set processes for development (unlike Waterfall) and there are no actual rules because of the need to move quickly and adapt. Each type of Agile development does have a prescribed set of methodologies which all team members should be familiar with and follow.

Better than any Methodology: Listen to One Another Acknowledging input from other team members and stakeholders does not mean forming judgments about it When we listen we are exposed to and have the opportunity to recognize additional facts from multiple viewpoints so that we can make a wise choice based on how things are for all involved — not how we think they are or want them to be