IMO, _you_ do not "write stories." PMs/POs do not write stories. Nobody inside your org writes stories. Instead, capture them from your user/customers. They emerge from conversations. Listen closely. Capture what's important.
Imagine that you're building a boring CRUD app ... a server-side rendered web application talking to a relational database. Perhaps we choose Java/Spring Boot and MySQL.
Hypothesis: the moment a team adds the requirement that each PR/commit should be related to a Jira issue, it will start accumulating even more tech debt than before.
This requirement adds a penalty for making small, unrelated improvements that get the project in a better shape.
Let's start a campaign for NEGATIVE LINES-OF-CODE contributors in brown-field code-bases. Next-gen rockstar programmers.
"I will strip 100 of LOC liability from your code monthly."
Look from far enough away, all a developer does is type.
Pull requests. Invented to manage large open-source projects, currently wrongly seen as a way to conduct code reviews. Why is it the general advice to not do them?
🗣 Join @davefarley77 in his exploration of pull requests and their alternatives.
https://t.co/2EVgDbukK2
Oftentimes you meet people who claim "TDD doesn't work". Not sure what exactly those people mean by "doesn't work"? It's often like saying "investing your money doesn't work". Yeah, if you're not good at investing, for sure it doesn't work.
"Do Continuous Integration." "Code reviews have sucked since the beginning of time. If you need four eyes on the code, try pair programming." - Erik Dörnenburg @GeeCON
Public institutions spend millions on software development projects 🧑💻👨💻👩💻
But, these projects often fail or underdeliver massively 💸
Here is how taxpayer money can be saved 💰 by training developers in Test-Driven-Development 🤷♂️
🧵 👇
If you think you must do something (e.g. Sprints, backlogs, story points, estimation, meetings, &c.) to be Agile, perhaps you don't fully understand what Agile is. It has nothing to do with rigid practices or frameworks. See https://t.co/Q8eHPEMzF8
💯 A professional cook doesn't ask for permission to clean their tools, before moving on to the next dish.
Refactoring is the same.
We should not ask permission to do a professional job!!
"No Estimates" is the _result_ of adopting agile ways of thinking and working, not a goal or directive. Work in a way that estimates aren't necessary or desirable in an org with a culture of trust, and you will have no estimates.