Repository navigation
Agile Process
Product Owner
The Product Owner (PO) is responsible for maximizing the value of the product resulting from work of the Development Team. The PO is responsible for the following topics:
-
Managing the Product Backlog. Product Backlog management includes:
- Clearly expressing Product Backlog items;
- Ordering the items in the Product Backlog to best achieve goals and missions;
- Optimizing the value of the work the Development Team performs;
- Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,
- Ensuring the Development Team understands items in the Product Backlog to the level needed.
-
Sprint Planning 1
- Planning of user stories
- Chooose responsible developer for user story
- Set up meeting
-
Set up Groomings if necessary
-
UAT
-
Communication with stakeholders
Scrum Master
The Scrum Master (SM) is responsible for promoting and supporting Scrum as defined in the Scrum Guide. SM do this by helping everyone understand Scrum theory, practices, rules, and values. He/She is responsible for the following topics:
- SM service to the PO
- Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible;
- Finding techniques for effective Product Backlog management and helping the Scrum Team understand the need for clear and concise Product Backlog items;
- Understanding product planning in an empirical environment;
- Ensuring the PO knows how to arrange the Product Backlog to maximize value;
- Understanding and practicing agility; and,
- Facilitating Scrum events like Sprint Planing 2 or Retropersectives as requested or needed.
- SM service to the Development Team
- Coaching the Development Team in self-organization and cross-functionality;
- Helping the Development Team to create high-value products;
- Removing impediments to the Development Team’s progress;
- Facilitating Scrum events as requested or needed; and,
- Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood.
- Share Screen in Daily and guide through Daily
Development Team
The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint.
Development Teams have the following characteristics:
- They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality;
- Development Teams are cross-functional, with all the skills as a team necessary to create a product Increment;
- Scrum recognizes no titles for Development Team members, regardless of the work being performed by the person;
- Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis; and,
- Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.
DevOps To make it clear, DevOps engineers should concentrate on one thing, and one thing only: cloud infrastructure management.
- DevOps Evangelist — The principal officer (leader) responsible for implementing DevOps
- Release Manager — The one releasing new features & ensuring post-release product stability
- Quality Assurance — The one who ensures the quality of the product confims to its requirement
- Security Engineer — The one always monitoring the product’s security & health
- (Software Developer/ Tester — The one who develops the code and tests it)
- When a task/bug is started, it is assigned to this person and pushed to "Active".
- When the PR is created, the status is changed to "In PR".
- If the PR is completed, developer tasks are moved directly to "Closed" and UAT tasks or bugs are moved to "Ready for Testing".
- If a bug from the "Ready for Testing" column is not fixed, it is moved to the "Open" column. Additionally a comment is written in the bug
- If there are blockers for further processing (e.g. waiting for feedback from stakeholders/PO), Blocker = Yes is set and the task/bug automatically changes color
- Regularity: Daily
- Participants: Scrum Team
- Duration: max. 20min.
- Person responsible for the meeting: Scrum Master
- Content
- What was implemented yesterday?
- What will be implemented today?
- Responsibility for stories/tasks is created
- Regularity: If there is a need
- Several days before end of sprint - at least 2 days before end of sprint
- Participants: Scrum team
- Duration: max. 90min. per appointment, several appointments possible, up to max. 4 hours per sprint
- Person responsible for the meeting: PO
- No preparation by the development team necessary
- Content
- Features and associated stories are presented (what and why)
- Functionality is discussed (how)
- Determine effort
- Prioritisation (what needs to be done first)
- (Describe possible tasks)
- Goal: Build understanding of feature/stories and remove ambiguities Definition of Ready is met
- Regularity: Sprint start
- Participants: Scrum team
- Duration: 30min.
- Person responsible for the meeting: PO
- Content: What user stories will be implemented
- Regularity: Sprint start after SP1
- Participants: Development team
- Duration: 60min
- Person responsible for the meeting: Development team
- Content: Define tasks for user stories
- Regularity: End of sprint
- Clarify in the Daily whether the meeting is necessary
- Participants: Scrum team
- Duration: 30min
- Person responsible for the meeting: Scrum team
- Content
- Have we reached our sprint goal?
- How can we improve the cooperation in the team?
- How can we optimise the product quality?
- Regularity: End of sprint
- Participants: Scrum Team + Stakeholder
- Duration: max. 2hour.
- Person responsible for the meeting: Scrum team
- Content:
- What was set to "Done" in the last sprint?
- What is next in the timeline?
In agile software development, the term "Definition of Ready" (DoR) refers to a set of criteria or conditions that a user story or product backlog item must meet before it is considered ready to be taken up by the development team for implementation.
An item is ready to be taken into a sprint, if the following criteria are met:
- It's part of the Product Backlog
- It has a defined value for the product
- It has been prioritized in a sprint Planing for the next sprint iterarion
- The item has been estimated in the beginning of a sprint iteration
- Acceptance criteria are defined
- Acceptance criteria cover the handling of error cases
- If it's a bug, it was successfully reproduced as described by the reproduction steps
- It was refined by the team at least once
- The team is able to estimate the item with respect to uncertainties and dependencies in the sprint planning
- The team has estimated the item and discussed approaches while doing so
- The team has understood the item.
- The team has decomposed the item into Tasks and estimated them optionally
- It's decomposed so that we don't exceed a sprint
- Dependencies of this item have been adressed / been marked as Done
The Definition of Done (DoD) determines when a User Story can be called done. The Definition of Ready (DoR) determines whether a Product Backlog Item is sufficiently described to be included in a Sprint Backlog.
In agile software development, the "Definition of Done" (DoD) is a set of criteria or conditions that must be met for a user story, feature, or task to be considered complete and ready for release. An item is done if the following criteria are met:
- Code is written and the prodcut can be built without errors
- Tests are written and passing as discussed in the DoR
- Documentations are up to date
- Migration scripts are up to date and tested
- Acceptance Criteria of the Backlog Items are met
- Changes are merged back to master or respective release branch
- The code is reviewed / PR review and accepted by at least 1 developer
- While testing a Developer should try to find exploits in the Feature. The Developer should try to break the application or find security vulnerabilities in a manner a malicous user is capable.
- Item is tested against acceptance criteria by the Product Owner. Test and test results are noted
- The Story has no critical bugs
If possible, the person with the most knowledge in the affected area should review the pull request to ensure proper feedback.
When reviewing pull requests the following criteria should be checked.
- Merge into correct branch
- Release branch / master / feature branch
- Code matches tasks
- There is code that doesn't match a task? --> Task should be linked
- Check if the code does actually fix what linked tasks describe
- If Migration included
- Check if CD build throws no errors
- Check general code guidelines were complied
- If Tests were written
- Check that tests make sense
- Enough test coverage was provided
- Most important cases are covered
The basis for a user story estimate is a story that requires a PT (Poker Time) for the complete implementation. This story is given an SP (Story Point). Subsequent user stories are set in relation to this.
The following topics must be considered for Story Points estimation:
- Volume & Knowledge
- Number of areas to be adapted (code areas)
- New feature or already existing in similar form
- PR Review
- Refactoring
- Complexity
- Uncertainty
- Learnings from the last estimates
Subsequently, a fixed percentage is added to the SP estimate for tests.