Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile project management_with_scrum_-_book_notes


Published on

  • Hey, the slides are very useful and informative. I liked your approach very much, and it has all the details related to the topic! I just wanted to share this link so you could find some other great resources for scrum and Agile through this FREE Book on SCRUM, download here
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

Agile project management_with_scrum_-_book_notes

  1. 1. Visibility Empirical Process Def Inspection Apendix A has great high level rules Rules Adaption Teaches scrum to other members Scrum Master Ensures the scrum process is followed and successful Represents the interests of the stakeholders 30 Day Iteration Always changing Time Boxed: 8 Hours Maximum Initial estimates and priorities Product Owner and Team Chosen based off priority of Product Backlog Provides initial overall requirements meet to discuss what will be the Product Backlog Dynamic, always updating Product Owner (PO) done for the next sprint and changing Team should practice communication Large Printout in team area so skills with the Product Owner to speak everyone knows the goals and about business not technically progress Work with PO to update/ Discussion includes content, purpose, add to and prioritize meaning, and intentions of the Product Focused on Return on Roles First 4 hours Product Backlog Backlog. Investment (ROI) Responsible for developing Agreed upon tasks are called functionality Sprint Planning Meeting Sprint Backlog Team May not be complete/comprehensive but Self managing and self organizing enough to get the team started and on track Responsible for success of Team creates a plan to work to complete all tasks each iterration 2 Parts off agreed upon tasks Estimations need to include Second 4 hours Tasks are created and assigned design, unit testing, All role members have refactoring, peer review Those not committed cannot intefere Committed to the project authority in each area Estimate hours on task Should include formal testing tasks until Thus the pig is the only real the team understands done means committed role Pig and Chicken discuss everything from desing->code->refactor->fully Only going to serve Ham and Eggs opening a restaraunt Pigs and Chickens analogy testedChicken desires the project to besuccessful, but has no real work Marks the beginning of the 30to do and isnt on the hook for day sprintits success Sprint Agile Project Management With Every Day 15 min Scrum - Roger Lopez What have you done since the last scrum Answer Three Questions What you plan on doing until the next scrum What roadblocks you have Daily Scrum for this sprint or the project One member from each team Synch up team and schedule any find out what is behind and if meets for a separate daily meetings needed to forward its all tasks are going to be scrum Scrum of Scrums progress finished A team member from one team will take part in allow team members to other teams daily scrums to coordinate Mention detail Do NOT say bug fixes state which bug, in what code offer help or insight dependencies. This makes them a part time team member. Part time team members Find out who needs help schedule help asap Should replace formal Time Boxed: 4 Hours documentation and reporting on the Sprint Review Meetings can sprint be mixed as a demo day Sprint Review Team presents what was developed to the Product Sprints to setup archiecture Owner Other stakeholders can attend required before scaling teams Adding Number of Teams Complex Projects New teams are seeded with a Time Boxed: 3 hours member of original team ScrumMaster encourages the Team to Decompose business architecture to Sprint Retrospective Meeting revise, within the Scrum process framework support clean-interface multi- team and practices, development Scaling Scrum Non functional scaling requirements Each team member states what worked Decompose system architecture to need to be added to product in the sprint and what needs to be support clean-interface multi- team Staging backlog improved development. If necessary, define and implement a development environment to support multi-team collocated or distributed environments.