Do you have users who are excited about logging in? They brag about how they logged in to their friends. They feel a sense of achievement because they've logged in!
No.
No value == not a story.
I'm going to beat this horse until it sinks in. Workflow steps are NOT stories.
There's never enough time upfront. There never will be.
In any system that's larger than one or two human beings' memories, you can't have that perfect, clairvoyant, comprehensive, ideal software document.
Project Lead is not a role in Scrum. That’s not an inadvertent omission. Teams that are treated as children will never become real self-managing Agile (or Scrum) teams. 4/4
The biggest problem with scrum, and this is almost universal, is that the people who have been doing “scrum” for years have never ever seen scrum done, and have never read the rules of scrum, and frankly don’t understand any of it.
Start with the smallest possible thing you can build that barely meets a single need of a handful of users. Build that. Release it. Have a conversation and get feedback. Using that feedback, make a single small modification and release again. Repeat until the users are happy.
That's like saying a hammer is easy to use but difficult to master. No a hammer is relatively easy to master as I learned one summer helping a friend build a house. But building a house is difficult to master. 5/5
Unless your nerves start making you double guess yourself or worry and not focus or fill your mind with worry rather than problem solving or worry affects your memory recall or OMG DID THEY JUST ASK WHAT A CLOSURE IS?!? WHAT EVEN IS A FUNCTION!!!!
(And please don’t trot out that "design is necessary" chestnut. Sure it is, but that doesn’t mean you need to do it up front. Design incrementally as you learn.)
It’s all very, very simple. If I improve my tools/skills/knowledge, I’m faster next sprint. If I work harder, I’m no faster next sprint. – Tim Ottinger
#agile