Presentation on theme: "What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration."— Presentation transcript:
1What is Agile?Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change
2What is Scrum?SCRUM is one of many Agile process frameworks that allows us to focus on delivering the highest business value in the shortest time.It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month).The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features.Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.
5Roles Product Owner Scrum Master Team Defines the features of the product, decides on release data and contentIs responsible for the profitability of the product (ROI)Prioritizes features according to market valueCan change features and priority every 30 daysAccepts or rejects work resultsScrum MasterEnsures that the team is fully functional and productiveEnables close cooperation across all roles and functions and removes barriersShields the team from external interferencesEnsure that the process is followed: Invites to daily scrum, iteration review and planning meetingsTeamCross-functional, seven plus/minus two membersSelects the iteration goal and specifies work resultsHas to the right to do everything within the boundaries of the project guidelines to reach the iteration goalOrganizes itself and its workDemos work results to the Product Owner
6Ceremonies Sprint Planning Sprint Review Sprint Retrospective Team selects items from the product backlog they can commit to completingSprint backlog is createdHigh-level design is consideredSprint ReviewTeam presents what it accomplished during the sprintTypically takes the form of a demo of new features or underlying architectureInformalWhole team participatesInvite the worldSprint RetrospectivePeriodically take a look at what is and is not workingTypically 15–30 minutesDone after every sprintDaily Scrum MeetingDaily 15 minute meetingsNot for problem solvingWhole world is invitedOnly team members, ScrumMaster, product owner, can talkEveryone answers three questions (What did I do yesterday, What will I do today, Is anything in my way)These are not status meetings for the ScrumMaster, they are commitments to your peers
7Artifacts Product Backlog The requirements A list of all desired work on the projectIdeally expressed such that each item has value to the users or customers of the productPrioritized by the product ownerReprioritized at the start of each sprintSprint BacklogCreated during sprint planning meeting and is the list of stories identified by the team for the SprintTypically the list contains the tasks associated with each story and hours or points to complete the taskList is updated daily by the team to reflect what has been completedBurndown ChartsEstimated work remaining in the sprint is calculated and graphed by the ScrumMasterUsed to manage Sprint goal
8Differences between Scrum and current Waterfall method Product Centric; you won’t hear the word projectProduct Owner leads by conveying the vision and represents the stakeholdersProduct Backlog is full or enhancement requests and defects; some of which may never be addressedNo project manager; Dev Team plans their own work and plans can change every sprintScrum Master is responsible for team following the process (not responsible for planning or acquiring resources)Sprints result in work that is “Potentially Shippable Software”
9Scrum in real life Need premise buy-in: Product owner is critical Some things sooner better than everything later90% accurate in 1 month better than 100% in 3Product owner is criticalResource intense“Refactoring” part of the processReporting entirely differentGet developers involved in stories early
12Discussion Points Resourcing product lines and managing capacity Who takes on the role of product manager and manages customer expectationsHow do you know whether to use waterfall or agile?Project selection vs product managementTaking on different roles – no more project managers, self-managed teams, where does the scrum master come from?