I’ve read quite a few books on agile development and writing user stories, and have read “if the story is too big, break it down into smaller steps”.
I’m struggling with what to do when a story is small from the user’s point of view, e.g. “As an administrator, I want to create a new customer”, but requires several steps on the backend to complete this, e.g. setting up FTP accounts, adding customer admin accounts, creating directories etc.
I know I can put these as acceptance criteria, but it feels wrong, particularly as it makes estimation difficult.
Does anyone have any advice on this? Is it acceptable to have tasks that aren’t strictly user stories in the backlog?