Agile Project Management

Click here to load reader

download Agile Project Management

of 29

  • date post

    22-Jan-2017
  • Category

    Documents

  • view

    186
  • download

    0

Embed Size (px)

Transcript of Agile Project Management

Agile Project Management

Agile Project ManagementCici Conger PortieCertified Scrum Product OwnerPMI-ACP, PMP, PgMPhttps://www.linkedin.com/in/cicicongerportie

1

What is Agile?

2001Wikipedia, a Wiki free content encyclopedia, goes online Napster is closed down by court order following an injunction on behalf of the Recording Industry Association of America (RIAA), The code red ( WORM ) virus attacks 1/4 million web sites running on Microsoft's IIS web server Apple Computer releases the iPod. HP ( Hewlett Packard ) and Compaq Merge Microsoft releases Windows XP

Agile: A Short History2001: 17 thought leaders in the software development industry came together to discuss what had become bureaucratic, slow, and overly regimented software development practicesGoal: A new, Light-weight approach allowing for quick responses to change and frequent delivery of working software

The Agile ManifestoIndividuals and interactionsOver processes and toolsWorking softwareOver comprehensive documentationCustomer collaborationOver contract negotiationResponding to changeOver following a plan

The Twelve Principles of Agile Software developmentWe follow these principles:Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.Business people and developers must work together daily throughout the project.Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

The Twelve Principles of Agile Software We follow these principles:Working software is the primary measure of progress.Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.Continuous attention to technical excellence and good design enhances agility.Simplicity--the art of maximizing the amount of work not done--is essential.The best architectures, requirements, and designs emerge from self-organizing teams.At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Scrum Methodology

5 EventsSprintsDaily Scrum Meeting AKA StandupsSprint Planning MeetingSprint ReviewSprint Retrospective

3 ArtifactsProduct BacklogSprint BacklogDefinition of Done

Story Mapping the Product Backlog

These arent User Stories!They are actions or functions. Walking Skeleton

Sprint BacklogUser stories are short, simple descriptions of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system.

They typically follow a simple template:As a , I want so that .

Scrum BoardSimilar to a Kanban Board

Key Benefit: Visibility

Definition of Done

Criteria for completing a user story.

Should be created and agreed upon by the team.

Should be visible to the team.

3 Team RolesProduct OwnerResponsible for maximizing the value of the product, organizing/prioritizing backlog, sharing vision of the productScrum MasterEnsures Scrum is understood and used, removes impediments to progress, facilitates events, servant leaderDevelopment TeamEmpowered to manage their own work, self organizing, cross-functional, members can fulfill multiple roles on the teamWhere is the project manager?

The Role of a Project Manager in an Agile WorldFacilitating Scrum of ScrumsDriving issues to resolutionTracking and managing cross project / program dependenciesHelping the teams stay focused

Leading Scrum of ScrumsIdentifying cross team dependencies; risksManaging timeline against which scrum teams work16

Planning a Project without a PlanTeam with the Product Owner to plan releasesWork with the Product Owner and Scrum Master to develop a rough schedule back from the release plan into a high level view of the sprintsWith Multiple Customers work to help define customer specific filters of the backlogEnsure customer requirements make it into the product owners list for inclusion in the backlog

things to look for when considering the use of agileManagement Stakeholder Buy-InIndependent projects with high degree of changeTeams that are co-located or that have and are comfortable with virtual co-location toolsDevOps teams

Discussion:Non-Software Development Projects that could use AgileExample: Infrastructure Projects with a high degree of change AND that does not require a sequential approach:Data Center Shut-downs, MigrationsEnterprise wide Database or OS Upgradeswhat projects can you think of?

Case Study Right Sizing ProgramRight Sizing Program GoalsReduce the footprint consumed by a companys server farmReduce the amount of power consumed by a companys server farmBY: Reducing the infrastructure of all applications from the size required to support 10 million customers to the minimum size required to support approx. 3.3 million customers

ApproachIdentify exact infrastructure for all applications Web ServersApp ServersDatabase ServersSAN ComponentsReduce all highly available components from 3 way to 2 wayConsolidate like technologies on to smaller, more flexible hardwareAs hardware is freed up, decommissionProvide daily reporting on changes, decommissions, and power reduction

Making it HappenSet up virtual co-location for development and PM teamDaily Live Bridgeline, all team members can openAll team members have access to sharing softwarePhase 1: A Date for A Date: Preparing the BacklogDevelopment team builds data management site with reporting to support the goalsPgMs meet with SMEs across the org to gather the data and input to the data management sitePhase 2: Migration and Decommissions Additional PMs + development team + management hold daily standup to review what happened yesterday, what plan is for the day, any issues or impediments to progressPgMs keep scrum board up to date and run sprint scenarios dailyPgMs & development team create sprint backlog every 2 weeks

Whats the Point?Scrum Perfection?

Nope. Exceptional Delivery.

24

25

OutlineTopicApproachWhat is Agile?Short HistoryAgile ManifestoLectureScrum Methodology5 Events; 3 Artifacts3 Team RolesLectureProject Planning in an Agile Project FormatLecture / DiscussionQ & ADiscussion

Description of SessionNew to the concepts of the Agile approach to project management? Wondering how project managers play into the Agile methodologies? Wondering if your project can benefit from some of the Agile concepts?This session will share the basics of Agile with you and provide you with a forum in which to discuss issues or questions about the application of Agile to any kind of project situation.

Learning ObjectivesBy the end of this session the participant should:Know what the Agile Manifesto is and what it representsUnderstand the basics of one Agile methodology (Scrum)Understand the role of a project manager on an Agile teamHave food for thought when considering the use of Agile

About CiciCici Conger-Portie, PgMP, PMP, MBA has 19 years of program and project management experience. Building her skill set began with Big 4 training and consulting, Fortune 500 company consulting, internet start-up management positions, graduate school for business and PMP, PgMP, PMI-ACP + additional Agile certifications. In her spare time, Cici enjoys painting, reading, spending time in her flower garden and relaxing with friends.

29