Agile Project Management

Click here to load reader

download Agile Project Management

of 39

  • date post

    22-Feb-2016
  • Category

    Documents

  • view

    66
  • download

    0

Embed Size (px)

description

Agile Project Management. Presented by: LongNH Date: February, 2011. 1. Before Start. 2. Content. 3. Agile Scum. Principles. Agile. Framework. Scrum. XP. Practices. 4. Agile Manifesto. Individuals and Interactions. Processes and Tools. Working Software. - PowerPoint PPT Presentation

Transcript of Agile Project Management

TFS 2010 Presentation

1

Agile Project ManagementPresented by: LongNHDate: February, 20111 1

Before Start..23Content3Agile Scum4AgileScrumXPPrinciplesFrameworkPracticesAgile Manifesto5Processes and ToolsComprehensive documentationContract NegotiationFollowing a planIndividuals and InteractionsWorking SoftwareCustomer collaborationResponding to Change6

7

Scrum Framework8Product ownerScrumMasterTeamRolesSprint planningSprint reviewSprint retrospectiveDaily scrum meetingCeremoniesProduct backlogSprint backlogBurndown chartsArtifacts

Define the features of the productDecide on release date and contentBeresponsible for the profitability of the product (ROI)Prioritize features according to market value Adjustfeatures and priority every iteration, as needed Accept or reject work results

Product Owner9Scrum Master10

Represents management to the projectResponsible for enacting Scrum values and practicesRemoves impediments Ensure that the team is fully functional and productiveEnable close cooperation across all roles and functionsShield the team from external interferencesScrum Team11

Typically 5-10 peopleCross-functional:Programmers, testers, user experience designers, etc.Members should be full-timeMay be exceptions (e.g., database administrator)Teams are self-organizingIdeally, no titles but rarely a possibilityMembership should change only between sprintsProcess12 Sprint Planning Meeting Sprint Daily Scrum Sprint Review Meeting

Sprint Planning Meeting A collaborative meeting in the beginning of each Sprint between the Product Owner, the Scrum Master and the Team Takes 8 hours and consists of 2 parts (before lunch and after lunch)

13Parts of Sprint Planning Meeting1st Part:Creating Product Backlog Determining the Sprint Goal. Participants: Product Owner, Scrum Master, Scrum Team2nd Part:Participants: Scrum Master, Scrum TeamCreating Sprint Backlog

14Pre-Project/Kick off Meeting A special form of Sprint Planning Meeting Meeting before the begin of the Project

15Sprint A maximum month-long iteration (2~4 weeks), during which is incremented a product functionality NO outside influence can interference with the Scrum team during the Sprint Each Sprint begins with the Daily Scrum Meeting16Daily Scrum Is a short (15 minutes long) meeting, which is held every day before the Team starts working Participants: Scrum Master (which is the chairman), Scrum Team Chickens and Pigs Every Team member should answer on 3 questions

173 Questions in Daily Scrum What did you do since the last Scrum? What are you doing until the next Scrum? What is stopping you getting on with the work?18Daily Scrum Is NOT a problem solving session Is NOT a way to collect information about WHO is behind the schedule Is a meeting in which team members make commitments to each other and to the Scrum Master Is a good way for a Scrum Master to track the progress of the Team19Sprint Review Meeting Is held at the end of each Sprint Business functionality which was created during the Sprint is demonstrated to the Product Owner Informal, should not distract Team members of doing their work20Scrum Artifacts Product Backlog Sprint Backlog Burn down Charts21Product BacklogRequirements for a system, expressed as a prioritized list of Backlog ItemsIs managed and owned by a Product OwnerSpreadsheet (typically)Usually is created during the Sprint Planning MeetingCan be changed and re-prioritized before each PM22Sprint BacklogA subset of Product Backlog Items, which define the work for a SprintIs created ONLY by Team membersEach Item has its own statusShould be updated every day

23Sprint BacklogNo more than 300 tasks in the listIf a task requires more than 16 hours, it should be broken downTeam can add or subtract items from the list. Product Owner is not allowed to do it

24Burndown ChartsAre used to represent work done.Are wonderful Information Radiators3 Types:Sprint Burn down Chart (progress of the Sprint)Release Burn down Chart (progress of release)Product Burn down chart (progress of the Product)25Burndown ChartsX-Axis: time (usually in days)Y-Axis: remaining effort26Sprint Burndown ChartsDepicts the total Sprint Backlog hours remaining per dayShows the estimated amount of time to release Ideally should burn down to zero to the end of the SprintActually is not a straight lineCan bump UP27Release Burndown ChartsWill the release be done on right time?X-axis: sprintsY-axis: amount of hours remainingThe estimated work remaining can also burn up

28Alternative Release Burndown ChartsConsists of bars (one for each sprint)Values on the Y-axis: positive AND negativeIs more informative then a simple chart29Product Burndown ChartsIs a big picture view of projects progress (all the releases)30Scaling ScrumA typical Scrum team is 5-10 peopleJeff Sutherland - up to over 800 people "Scrum of Scrums" or what called "Meta-ScrumFrequency of meetings is based on the degree of coupling between packets31Scrum of scrums

32Scrum of scrums

33XP@ScrumScrum is an effective project management wrapper for eXtreme Programming development practices, which enables agile projects to become scalable and developed by distributed teams of developers.

34Pro/ConAdvantagesCompletely developed and tested features in short iterations Simplicity of the processClearly defined rulesIncreasing productivitySelf-organizingeach team member carries a lot of responsibilityImproved communicationCombination with Extreme ProgrammingDrawbacksUndisciplined hacking (no written documentation)Violation of responsibility Current mainly carried by the inventors35Teamwork

36Teamwork37

Teamwork38

ConclusionIt is not the strongest of the species that survive, nor the most intelligent, but the ones most responsive to change.

- Charles Darwin, The Origin of SpeciesWork hard Have fun Make a differenceThanks for your attention!Questions?

39