User stories are a common practice in Agile but what are they and why do we use them? Read about my experience here, plus if you get to the end there is a useful story writing handout.
Latest information from Radtac
We are living and working in an ever more rapidly changing world, in this blog I will start to explore how organisations can do more with LeSS.
For many years Radtac has been delivering Agile Virtual Training as well as our Classroom, Video and eLearning training services. Whether online or offline we always provide the best learning experience. Given the current global condition Don't Panic - we know that most of our customers are currently facing travel bans and isolation which means that our Agile Virtual Training is the best solution available.
We are massively proud to announce that Radtac has received the award of the Most Innovative Business Transformation Consultancy UK 2019!
I love mince pies. FACT.
It was a day in late November, and I was catching the late train home after a long day in the office. I needed a drink, so I went to the food and drink place in St Pancras International. I asked for my coffee, and was offered a Mince Pie for an extra £1. Ooh that’s a good offer, I thought, so I said ‘Okay’.
Whilst sitting on the train I sipped my drink and devoured my Mince Pie. The coffee was good, but the mince pie was average at best. Especially for a £1, I thought. Perhaps it wasn't such a good deal!
So I posted a picture of my pie to our Slack channel, and jokingly gave it a score of 6 out of 10. Our Slack channel went berserk with ‘You’ve had a mince pie - why have you scored it?’ ‘OMG you scored it’ etc. And I thought, well yes, I have had a mince pie, and yes I have scored it... I wonder how others compare, and I wonder which one is best!
And that is where it all started.
It’s 1989 in San Dimas, California, and strange things are afoot at the Circle K. Bill and Ted have been spending all their time trying to create a metal band - “Wyld Stallyns” - all at the expense of their education.
Somewhere in the future the year is 2688 A.D., and the world exists in an utopian society due to the inspirational “Wyld Stallyns”.
Little did Bill and Ted know the consequences of failing their final year at high school. A bogus outcome could have a devastating impact not just on their future, but also the whole of humanity. Ted’s dad would send him to military school if he failed his final history oral report, ending the chance of “Wyld Stallyns” being successful.
Contrary to what one might think, IT and the Business are not always perfectly integrated. Sometimes, there is a clear distinction between ‘Us, IT’ and ‘Them, the Business’, when in fact these two should never be separated. Here’s why.
When an organisation or a team are transforming their way of working from traditional to an Agile approach, traditional roles like Business Analyst, which were a phase of a traditional project, don’t simply cease to exist - they transform into their Agile equivalents.
How does an Agile Business Analyst differ to a traditional Business Analyst? Well, there will be a lot of similarities, but also possibly some stark differences.
This blog post will explain what Agile Requirements are, and guide you through writing and using User Stories.
What are Agile Requirements?
As we cannot possibly know all requirements of our products at their inception, it is futile to spend time creating a detailed Requirements Specification Document upfront. Instead, we should use Agile Requirements.
Agile Requirements are requirements that are allowed to, in fact encouraged, to evolve over the lifetime of a product. We are learning more and more about our product during its development through feedback from Customers, Users, Stakeholders and Developers. Using this feedback, we can regularly choose to add requirements, remove requirements, add more details to requirements, change their priority, and so on, to make sure our Agile requirements will deliver the most value to the business as soon as possible.
This blog is a case study of an Agile implementation which started off as a classic Scrum implementation, and then evolved to use Scrumban and Kanban techniques.
In the Beginning.
It is day 1 of sprint 1 for a team.
To set some context, a Business Analyst had spent several months preparing a product backlog of nicely written user stories. They were conveniently written in the user story format:
‘As a <who>’
‘I want <what>’.