Principles
- Customer satisfaction by early and continuous delivery of useful software.
- Welcome changing requirements, even late in development.
- Working software is delivered frequently (weeks rather than months).
- Close, daily cooperation between business people and developers.
- Projects are built around motivated individuals, who should be trusted.
- Face-to-face conversation is the best form of communication (co-location).
- Working software is the principal measure of progress.
- Sustainable development, able to maintain a constant pace.
- Continuous attention to technical excellence and good design.
- Simplicity— only build what is really essential.
- Self-organizing teams.
- Regular adaptation to changing circumstance.
Rituals Of Agile:
- Sprint Planning-Discuss on User stories to Work
- Daily Stand Ups- !5 mins meetings/Kanban Board
- Sprint Reviews -Planning for 2 weeks(Demo/Showcase)
- Retrospectives-Meetings done after Sprints to Review (What went well/What dint/What should)
Key concepts
- User Stories :User stories are basically product features, requirements or tasks that add value to the end customer.Most Agile Teams use user stories as tasks that reflect what they are trying to accomplish, which of course is directed to meeting a customer need or requirement. • As a (who) I want… so that… • + story points + acceptance criteria. Should be independent, negotiable, valuable, estimable, sized appropriately, testable (INVEST).
- Story points • Story points are a relative unit of measure to assess whether a user story is big or small. You can use different scales for story points (e.g. 1, 3 or 5 ; t-shirt sizes s, m, l, xl, xxl).
- Product Backlog • An ordered list of everything that might be needed in the product (also known as Master Story List). Sprint Backlog • The set of Backlog items selected to be delivered over a period of time.
- Sprint Backlog • The set of Backlog items selected to be delivered over a period of time.
- Velocity • The number of story points delivered over a sprint. Swimlanes • A visual representation of stories (y axis) vs. status on the kanban/agile board: To Do; Doing; Done (x axis). Swimlanes let the team see progress on individual stories, while highlighting specific areas that need attention.
- Minimum Viable Product (MVP) • The bare minimum product that meets the client’s expectations. Includes all must haves and excludes all nice to haves (no bells and whistles).
- Release • Comprised of several iterations or sprints. Sprint • A period of time in which the team will work on a defined set of user stories.
Great tools you can use for your Agile Projects
- Jira, Trello, Freedcamp, Asana, Basecamp, Active Collab, Workamajig,Teams,Planner
Process
| Agile / Scrum Knowledge |
| Overview provided for team |
| Any training identified |
| Any coaching /support requirements identified |
| Team Work Practices |
| Team Roles defined (Scrum Master, Product Owner, etc.) |
| Confirm Sprint duration and timing |
| Daily stand-up time and location |
| Team location |
| Team values and expectations |
| Definition of Ready and Definition of Done |
| Product/Project Vision |
| Overall vision & goals clearly defined |
| Minimum Viable Product identified |
| Priorities/Trade-offs defined |
| Key risks, constraints and dependencies identified |
| Key stakeholders mapped |
| Solution, Tools & Technology |
| High-level solution architecture defined |
| Path to production |
| Infrastructure/environments |
| Development tools |
| Scrum tools |
| Test tools |
| Team communication tools |
| Individual Equipment |
| Initial Backlog |
| Key Features/functions identified |
| Initial backlog of stories ready for development |
| Agile plan/schedule |
| Socialisation |
| Initial communications |
| Kick-off meeting to engage stakeholders |
sheetalatuxdesigner.com 