Agile - Scrum Presentation

of 18/18
Waterfall & Agile – Scrum (By: Gihan Wijesinghe – Professional Software Developer) TOPIC S: Waterfall & various other methodologies History of Agile, Manifesto, 12 Rules Various processes of Agile Introduction to Scrum framework Key roles in Scrum Key artefacts in Scrum Scrum ceremonials Conclusion
  • date post

    16-Feb-2017
  • Category

    Software

  • view

    245
  • download

    1

Embed Size (px)

Transcript of Agile - Scrum Presentation

PowerPoint Presentation

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)TOPICS:

Waterfall & various other methodologies

History of Agile, Manifesto, 12 Rules

Various processes of Agile

Introduction to Scrum framework

Key roles in Scrum

Key artefacts in Scrum

Scrum ceremonials

Conclusion

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)Software Development ModelsLinear FlowIterative FlowLinear & Iterative FlowWaterfallPrototypingIncrementalAgileSpiralRapid Application Development

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)By Dr. Winston Royce (1970) Waterfall Model

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)Waterfall Model best suite for:Project requirements & objectives are clear, not ambiguous and very rarely changing Project is large, expensive & complicated, client expect the formal approachesProjects cost is pre-defined, fixed-priceImmediate implementation is not requiredWhen resources need to be conserved

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)History of Agile, Manifesto, 12 Rules

Bureaucratic

Over Regimented

Slow

Difficult to enhanceSD models develop in 1970 1990 have been criticized by users as:

Industrial Experts / Thought Leaders

Promote innovative approaches to developments

Embracing requirement changes

Continual planning, Empowering teams, Frequent delivery of a working part

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)History of Agile, Manifesto, 12 RulesIn 2001, 17 Software consultants gathered to Snowbird, Utah (USA) & defined AGILE SOFTWARE DEVELOPMENT

Our highest priority is to satisfy the customer through early and continuous delivery of valuable softwareWelcome 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 conversationWorking software is the primary measure of progressAgile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitelyContinuous attention to technical excellence and good design enhances agilitySimplicity the art of maximizing the amount of work not done is essentialThe 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

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)Various subsets of Agile

Scrum is a management and control process that cuts through complexity to focus on building software that meets business needsExtreme Programming (XP) is a pragmatic approach to program development that emphasizes business results first and takes an incremental, get-something-started approach to building the product, using continual testing and revision.Crystalis a family of human centric, adaptive, ultralight, stretch-to-fit software development methodologies

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)SCRUM FrameworkPart of an Agile movement use for product developmentIntroduced by Jeff Sutherland in 1993 (before describe the Agile)Project management framework applicable to any project (not only for software)Project move forward by series of iterations called sprints

3 Roles3 Artefacts4 Ceremonials

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)Key Roles in SCRUM

Product Owner

Scrum MasterTeam

Only one person, Responsible for maximizing the value of the productResponsible for managing the product backlogPerson who lead the development team & create a bridge between customer and developer parties. Need a wide range of knowledge & Skills, Sometimes act as a business requirement analystRepresents the interests of clientFacilitate the PO & team, facilitate to Scrum ceremonialsEliminate any obstacles which restrict the team when achieving the sprint goalHe / She might be a dedicated full time scrum master or a team memberNot a project manager / does not manage the team, But help to take the decisionsMake sure that everything is happening according to the scrum processSelf organizing, Cross functionalNo sub teamsSoftware engineers, QA engineers, Architectures, UI designers etc.

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)Key Artefacts (1. Product Backlog)Contain the user stories (sample shows below) written by stakeholders & developersAll the user stories are unimplemented yet, No need to arrange them when starting pointEntire responsible of this backlog is up to Product OwnerNeed to arrange the features / user stories according to the priority level, before planning the sprints Never complete, will change consistently, will become larger when requirements are changingHR executive assign the salaries to new employees HR ex. Select the employee and assign basic salary, add fixed allowances, deductions & variable allowances, update data. Sometimes it is need to assign an entire salary scale. UI: http://demo.treinetic.com/RentchefnewTester will select employees and enter basic salaries & other info. Click the update button. Updated data will displayNameDescriptionScreensHow to testAs a HR Executive I can assign salaries to employees so that useful when preparing pay sheets

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)Key Artefacts (1. Product Backlog)

Simple example

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)Key Artefacts (2. Sprint Backlog)Contain the PBIs (Product backlog items) which are selected to particular Sprint, Items selected on Sprint Planning MeetingAlso contain a plan for deliver the relevant product incrementDevelopment team can change the SB during the sprintMust sort according to the priority order up to product ownerTime period will define for each member for each item

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)Key Artefacts (3. Burn down Chart)Graphical representation of the project progress with time will indicate hereUpdating the burn down chart should done by the scrum masterX axis represents the time by Sprints, Y axis represents the work load by story points (mentioned on PB)Release burn down chart is essential & team also can use spring burn down charts for each sprints.

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)Scrum Ceremonials (1. Sprint planning meeting)Product owner, Scrum master & Team will attend, Although not compulsory it is better to attend stakeholders as wellSort / Priorities the product backlog items (backlog refinement) by PO for upcoming sprint, Whole team must help him2 hours for the 2 weeks sprint / 4 for 4 weeksWhat is to be develop on the up coming sprint?How we are going to achieve that goal?

Sprint Planning MeetingProduct BacklogTeam & POSprint BacklogSprint Goals

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)Scrum Ceremonials (2. Daily Scrum Meeting)Every day during the sprint this meeting must held and discuss the progressScrum master & Team will attend, Scrum master should facilitate the meeting, PO is not compulsoryMaximum time will be 15 minutesEvery member need to explain three things:What I have accomplish after last meetingWhat Im going to do before the next meetingWhat are the obstacles I have encounter?

Improve the communicationIdentify the problems & obstaclesImprove the project knowledge of every oneScrum master MUST note all impediments & resolve them

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)Scrum Ceremonials (3. Sprint Review Meeting)Product owner, Scrum master, Team & Customers / Stake holders will attend1.5 hours for the 2 weeks sprint / 3 for 4 weeksEnd of the each sprint this meeting will held with working software part to inspect by customerTeam should demonstrate the increment with focus on the sprint goalPO, Team & stake holders will review the working part, Should not use slides, Working part is essentialCustomer / Stakeholders might ask some amendments, PO must note down themNew requirements might proposed & product backlog might be change as well as the priority order will change

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)Scrum Ceremonials (4. Sprint Retrospective Meeting)Product owner, Scrum master, Team will participate1 hours for the 2 weeks sprint / 2 for 4 weeksAfter the review meeting & before the next sprint meeting, this will heldTeam might revise their way of working in the past in order to make future works more efficiently Scrum master encourage the team to adopt best practice for the improvements of the next sprint

What should StartWhat should StopWhat should ContinueEven works are going well NEVER stop restrospective

Waterfall & Agile Scrum (By: Gihan Wijesinghe Professional Software Developer)CONCLUSION