- monerod.exe v0.12.2.0 out of sync
- Which American accent to learn for differentiating the most words
- Prevent replay attacks with signed inputs to smart contracts
- Async/Await problems with web3.eth.getAccounts
- Is the signature generated by “web3.personal.sign” different with “web3.eth.sign”?
- Basic Blockchain Implementation: how is the blockchain on a given node “synced” with that on another node?
- Quorum Private Transactions: Why public key instead of address?
- Is it possible to connect remix and Parity?
- What is the “clone-bin” output in solc?
- What laptop should I buy? (Web Developer, Linux)
- USB Still Camera (low cost)
- Is it legal to wait for insurance to clear before issuing a medical referral in the US?
- How to comply with CE marking regulation when importing into the EU/EEA?
- Does the United States legally not recognize phds from any spefic country?
- Не смог предотвратить что-то или чего-то?
- “Коту дали молока” - Родительный или винительный падеж
- О назначении на должность военрука + винительный или родительный
- Падеж в словосочетании “поили коня”
- Принятия к исполнению *постановлени(е/я)*?
- Правильное окончание
Team delivers needs a lot of time to deliver even the simplest stories- how to know why?
So, the problem, from the management perspective is that a scrum team delivers a only the simpliest stories within the whole sprint. Literally changing a button takes two weeks. The team estimates within a stable velocity, and mostly delivers everything that they commit to successfully.
I (a Scrum Master) have many suspitions why is that so, however I'd like to hear these problems directly from the development team. Do you have any tips on how to tackle this problem? What retrospective activities should I prepare for the team?
To clarify: I'm more than sure that the problem lies within the development process rather than the overall unwillingness to work.