Project Management & Collaboration Presented by Roni Banerjee, Medullus Systenms

Who am I?

Ok so this is me! Civil Engineer with a passion to create an IT company. Certified Project Manager (Project Management Institute). Started Medullus Systems in 2004. Delivered over 250+ projects – largest being a 4 year project involving 1,200 companies and a team of 150 members. Claim to fame – nothing yet, but that is why I get up every morning! Favorite past times – my guitars, cooking and golf – what has that got to do with Project Management? We will see…

Definition of a project It is a temporary means to achieving something permanent Temporary because every project has a definitive start and an end. Permanent because hopefully you will do something that will last a long time, maybe forever (Declaration of Independence, building the Golden Gate bridge, winning the World Series)

Triple constraint of every project Cost Quality Scope Time Quality: Delivering to scope as perceived by the primary stakeholder

Who is a Project Manager Someone who is “accountable” for the completion of a project (successful or unsuccessful), from “charter” to “close” 1 project should have 1 project manager Most important job of a project manager is “communication” If there are “n” members in a project there are n*(n-1) communication channels.

Some Project Managers you might know!

Project Management Components Scope, Cost, Time Risk Management Quality Management Stakeholder Management (a stakeholder is anyone is positively & negatively affected by the outcome of the project) Communication Management Resource Management Configuration Management Change Management

Those who forget history are condemned to repeat it! Structured PM can be traced back to early 1900s (Gantt Chart was developed in 1910). Over time it evolved into the traditional “waterfall” method – plan the whole project, set tasks, monitor and manage the tasks, close. Difficult to plan large projects in 1 shot Scope changes cause delays, cost overruns Agile became popular in the late 90s and formulated in 2001 (at a ski lodge in Utah!). Deliver a project in chunks (mini-projects) Talks about “backlogs” rather than “tasks” Quicker ROI (Return on Investment)

Scrum It is part of the “Agile Framework” Easy to understand – KISS principle (Keep It Simple St**id) Take the ENTIRE workload and divide into “chunks” that can be delivered as completed. Work on the 1st, deliver it, do a quick postmortem, move on to the next!

Let’s Scrum!

Scrum Roles Project: We need to win the Superbowl Stakeholders: Team owner, Investors (+), Other Team Owners (-) Business Owner: Team Owner Product Owner: Head Coach Scrum Master: QB Scrum Team Sprint: Every week we need to win a game (Break up the project into weeks) Daily Scrum: Meet to find out how we are prepping for the game, are we exercising, getting sleep, watching videos of the other team, figuring out the plays etc

Daily Scrum Meetings What did I do since we last met? What do I plan to do till we meet again? Anything roadblocks / showstoppers?

Risk Management What is a risk? Risk is any uncertain event that can have an impact on the success of a project (negative and positive) Ways to deal with risk Strategies for Negative Risk Driving to work Avoid Avoid the bridge – too much traffic Transfer Buy Insurance Mitigate Don’t text while driving Accept Can’t control the bad driver Strategies for Positive Risk Want to make money Exploit Buy a lottery ticket Share Let’s work together Enhance Shark Tank Accept Bank Interest

Closing a project Every project should be “Closed” whether it was successful or not (who decides if it is a success?) Document “lessons learned” What can we do better next time? What did we NOT measure this time? (you cannot improve what you do not measure!)

Other Project Management Frameworks Prince2 (PRojects IN Controlled Environments), MVP (Minimal Viable Product) Kanban Squads (Spotify) http://www.slideshare.net/JoakimSunden/agile-at-spotify

Summarizing Project is a temporary means to achieving something permanent Triple constraint – SCOPE, COST, TIME (with Quality in the middle) Anyone who is “accountable” for something is a project manager Traditional PM – waterfall  plan, work, deliver, close Scrum (Agile) – chunk, sprint, deliver, retrospect, repeat, close (daily scrum meeting) Roles – Stakeholder, Business Owner, Product Owner, Scrum Master, Team Risk Management (Postive, Negative) Remember to close EVERY project (successful and unsuccessful)

References & Further Research http://www.pmi.org http://www.scrumalliance.org You can find more info from these resources: http://y2u.be/D8vT7G0WATM http://scrumtrainingseries.com Or you can reach me anytime @ roni@medullus.com

THANK YOU ALL! Have a good weekend 