jambor.pro/docs-onboarding
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix Typo

Browse source
This commit is contained in:
Jan Jambor 2024-05-16 11:12:00 +02:00
parent 1592680085
commit 6399c627f7
1 changed files with 1 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

3
agile-working.md
View file

@ -10,13 +10,12 @@ Tools: MS Teams Channel
## Documentation
Everyone must have independent access to documentation, including specifications, decissions, and changes. We aim to work in a decentralized and asynchronous manner. Each individual should always be able to access all necessary information. We see documentation as a joint effort of all members and everybody should always improve documentation as needed. For some guidlines see [Documentation Guiidlines](documentation-guidelines.md), these should be rather interpreted as code of conduct than strict rules.
Everyone must have independent access to documentation, including specifications, decissions, and changes. We aim to work in a decentralized and asynchronous manner. Each individual should always be able to access all necessary information. We see documentation as a joint effort of all members and everybody should always improve documentation as needed. For some guidlines see [Documentation Guidlines](documentation-guidelines.md), these should be rather interpreted as code of conduct than strict rules.
Tools: Azure DevOps Repos and Wikis
## Meeting Minutes
Suggestion JJ:
Meeting notes are centralized taken as tasks in Azure DevOps. Everybody is responsible for them. If you hear something in a meeting that is relevant for you: add it as a comment during the meeting, after the meeting. The meeting minute tasks don't need a parent. They should follow a template (to be defined) and can be linked to Stories and other work items like Issues (Impediments) which have been discussed during the meeting.
Tools: Azure Boards Task