The Product Owner prioritizes the requirements or features through feedback from the Stakeholders & interaction with the core team The Team takes a subset of the prioritized features and works on them from development to testing in “Sprints” – short intervals of 2 weeks The Daily Scrums meetings are held for 15 minutes - same time, same place, every day The Team demonstrates what’s been completed by showing working software to the Stakeholders. The Product Owner accepts or rejects The Team continues with this process until the product is ready to implement for the business Business Vision Prioritized List of what is required, features, bug fixes Development, Testing, Documents Subset of the Priorities Features worked on in 2 Week “Sprints” Demo for Stakeholder Review/Feedback Delivery / “Release” of the Product SCRUM Retrospective Team dialog Stop/Start/ Continue Continual Iterative Process to Deliver Incremental Value

Ummmm, I dunno… Where’s my pizza? I have the munchies.

PPM system dynamically linked to Dev suite Work items/stories initiate in Dev suite, create tasks in PPM, tracked in Dev suite PMs order work according to plan, adjust schedules Resource utilization can be effectively tracked and reported

1. Allows work to be captured where people do their work 2. Provides both sides detail required to plan and deliver effectively 3. Doesn’t overly burden Agile dev teams away from their mission 4. PM gains insight real-time into work item status 5. Reporting relevance Requires two well-aligned systems and processes for effectiveness

PPM system used to create schedules, updated manually via team sessions Work items/stories live in Dev suite Alignment occurs via pure process Each team works in environment comfortable to them Doesn’t require systems integration

Collaboration, Communication, Alignment via meetings/conversation/other

1. Allows work to be captured where people work 2. Provides both sides detail required to plan and deliver effectively 3. Doesn’t overly burden Agile dev teams away from their mission 4. PM gains insight real-time into work item status Disadvantages 1. Manual cross-activity reporting 2. Opportunity for inconsistent data

Agile FrameworkHow ? A product owner creates a prioritized wish list called a product backlog. Agile / Scrum Teams here use Microsoft Team Foundation Server(TFS) to build and maintain their Product Backlogs. Each project in Project Server will have a Project Site for the storage of artifacts. Issues and Risks can also be maintained on the Project Site. During sprint planning, the team pulls a small chunk from the top of that wish list, a sprint backlog, and decides how to implement those pieces. TFS is used to house the Product Backlog and to select items to be included in the Sprint. Project Pro is used to manage the project schedule, which is visible to all users with access to project details via Project Server and the Project Site. The team has a certain amount of time, a sprint, to complete its work - usually two to four weeks - but meets each day to assess its progress (daily scrum). The developers use TFS to provide status on the specific work activities in the Sprint and the Scrum Master / PM uses Project Pro to manage the overall schedule. Other information can be stored on the Project Site. Along the way, the Scrum Master keeps the team focused on its goal. Notes can be stored on the Project Site

Agile FrameworkHow ? At the end of the sprint, the work should be potentially shippable, as in ready to hand to a customer, put on a store shelf, or show to a stakeholder. Any supporting artifacts (e.g., training materials, user guides, status reports, issues / risk logs, etc.) can be stored on the project site. The sprint ends with a sprint review and retrospective.The Review is a demo of capability delivered in the Sprint and the Retrospective is a lessons learned session … any notes documented from either session can be stored on the Project Site. As the next sprint begins, the team chooses another chunk of the product backlog and begins working again. TFS for the developers. Project Pro, Project Server and Project Site for the PM with visibility to other users (e.g., Team Members, Sponsors, etc.). The cycle repeats until enough items in the product backlog have been completed, the budget is depleted, or a deadline arrives. Which of these milestones marks the end of the work is entirely specific to the project. No matter which impetus stops work, Scrum ensures that the most valuable work has been completed when the project ends. Budget, schedule, deliverables, milestones … all can be managed and reported via Project Server.

Plan Gate Agile Objectives Sprint Develop ment Release Gate Sprint Gate Scrum Closure Product Release Methodology Filter Scrum Agile Waterfall SDLC New Project Vision  The Project Vision is common to both methodologies  The user get trained on Pros and Cons  Then choose the EPT which has the project embedded to it  PDPs are used at each phase to collect information Agile Process

MyPC fill out evaluations & win prizes! Fill out session evaluations by logging into MyPC on your laptop or mobile device. Evaluation prizes daily! Claim your prize at the Registration Desk on Level 1. After the event, over 100 hours of resources; including all of the PPT decks and session videos will be available.

Rob Hirschmann Projility Twitter: RobhProjility