The Theory & Praxis of Agile software development & Scrum by Gerald
 |
| https://www.planview.com/resources/guide/agile-methodologies-a-beginners-guide/basics-benefits-agile-method/ |
Objectives
- Be aware of agile principles & features of scrum framework Increase responsiveness of our work, be more value-centred in our delivery
- Be aware of agile principles & features of scrum framework Increase responsiveness of our work, be more value-centred in our delivery
Theory, Why Agile?
- Iterative approach to developing, delivering and sustaining complex products
- Project progress is continuous, incremental& value-driven
What differentiates Agile?
- individuals and interactions over processes and tools
- working software over comprehensive documentation
- customer collaboration over contract negotiation
- responding to change over following a plan
What are the Agile Principles?
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- Welcome 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. https://www.gif-vif.com/g/The-reality-of-communication
- 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 conversation.
- Working software is the primary measure of progress. (don't copy the form, you need to copy the substance, get your software to work!)
- Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
- Continuous attention to technical excellence and good design enhances agility.
- Simplicity –the art of maximizing the amount of work not done–is essential.
- The 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 behaviour accordingly.
What is Scrum?
A framework to practice agile that is based on empiricism which hinges on transparency, inspection& adaptationWhat are the features of Scrum?
- Self-organising teams
- Cross-functional, self-sufficient
- Value-based prioritisation
- Activities are time-boxed
- Iterativedevelopment
- Adaptive to change
- Clear enough roles & deliverables
- Inherently lean
How is a Scrum team configured?
Product Owner
1.Person responsible for maximising the value of the product & work done2.Manages& prioritises product backlog
3.Ensures product&sprint backlog is transparent& clear to all
4.Inspects&holds team accountable for sprint deliverables
Development Team
1.3 –8 people group responsible for doing the work of delivering a releasable product increment2.Works on tasks till it meets acceptance& done criteria
3.Self-organising, cross-functional
4.Flat structure, no titles or sub-teams
Scrum Master
1.Person responsible for promoting & supporting the practice of scrum2.Facilitates interactions within and outside the scrum team
3.Monitors, coaches, provokes changes to practices, the environment, behaviours to help the team succeed
How is Scrum practised?
Rituals
Sprint•Fixed, regular period of time (2 weeks) during which a releasable increment is created
•No changes to sprint back log once sprint starts
Planning
•Collaborative discussion (max. 2 hrs) to determine what can be done & how to get it done
•Product backlog to sprint backlog
•Sprint backlog(with criteria) to tasks
Scrum
•Daily 15 min to plan work for the day
•Allows team to inspect work done&sync efforts
•Focus on progress by eliminating impediments
Review
•1 hr at the end of each sprint to review product increment & inspect work done
•Review product backlog& prepare for next sprint
Retrospective
•1 hr at the end of each sprint to review how the teamworks
•Focus on inspection & adaptation to improve team efficacy & performance
Artefacts
Product Backlog•Ordered list of everything needed for the product
•Never complete but maintained by value-add priority
•Comprises user stories
•Includes acceptance& done criteria
SprintBacklog
•Pulled from the product backlog
•User stories are broken down into tasks
•Tasks under taken by members &with specific deadlines
Scrum Board
•Transparent, shared board showing work in progress
•Columns of product backlogs print backlog, sprint to-dos, sprint in progress, sprint to review, sprint done
Product Increment
•Sum of all product backlog items completed within a sprint
•Must be inspectable and useable
•May or may not be released
No comments:
Post a Comment