Hot answers tagged

3

TL;DR: No. Onboarding is a waste. Time and effort invested "Onboarding" is neither a functional or a non-functional requirement. In our project, we had failed to find how to address such situations within normal agile frameworks, and even on the agile manifesto itself. We went deeper and found a potential answer for such situations in agile's ...


2

Some examples of "sprint 1" stories for a e-commerce site: As a new customer I want the ability to sign-up for an account so that I can purchase As a potential customer I want to browse a catalogue of products Some examples for a HR application: As an HR user I want the ability to login As a HR user I want to retrieve an employee's details by ...


2

Non-functional requirements aren't an Agile concept - they very much pre-date agility. Non-functional requirements are about any of the criteria that don't relate to specific behaviors of the system under design. I don't think that an onboarding flow would be a non-functional requirement, but the attributes including usability, supportability, and ...


1

Don't get hung up on writing the perfect user story. Instead, if this is a new product that you are building from scratch, focus instead on: defining a big picture of what the product should do; split that vision into pieces, actions, and actors (you can use a technique called User Story Mapping for that, and create epics and user stories); place these ...


1

One user story will not give you a releasable product that represents some value to an end user This clause is added to get over the mindset of previous Waterfall practices. Doing analysis alone or doing design alone is not a valid user story. The story must result in some shippable code, which is what represents value to the user. can be delivered during ...


1

Apart from ashes999 great answer there is one more notable mention of how to introduce Agile into non-IT organization or team. I really like the part about not going with all the buzzwords and working mainly through Agile values perspective. There is a 5 step method according to this post: https://teamhood.com/agile/agile-for-non-it/ Educate people about ...


Only top voted, non community-wiki answers of a minimum length are eligible