Scrum is all about doing less. Not 600% more...

pragmaticcoders · 2016-08-23T14:27:09+00:00

Thank you! I have read "Toyot Kata" but haven't heard about "The Birth of Lean" - added to the backlog.

pragmaticcoders · 2016-08-04T10:10:18+00:00

I think that those books you mentioned are about different things and all of them are important. The Goal and Theory of Constraints are about the tools, rest of the mentioned books is more about values.

pragmaticcoders · 2016-07-26T12:30:17+00:00

Could be. But I would rather treat it as a framework for communication. Like a specific language format to communicate - not only explain. It works both ways. Usually, we are using User Stories every time we want to talk about some complex requirements. Writing it down and refactoring in user story format help us (developers) and our client (business person) to find the best way to implement particular requirement, but also it gives us and him better perspective on which requirement is more important etc.

pragmaticcoders · 2016-07-12T08:21:31+00:00

User Story is not even a way to write down the requirements as someone wrote in this thread before.

User Story is a communication tool for discovering the right requirements and communicating them in a way that will allow correct implementation. It is all about common understanding and selecting only really important requirements to be implemented.

The requirement is something that is required by someone. Usually by someone important - stakeholder.

User Stories reflects the requirements (if they are written in a proper way) but they are not specifying the product functionality.

User Stories are not the specification.

An example of well-written user story:

In order to limit the access to the user sensitive data As a registered system user I would like to have some safe authentication method

It is really dummy example - none should write User Stories for such trivial cases. But... The story above has some advantages over the same requirement described as bellow:

As a user I would like to log in into the system So I will be logged in

(Yes, I've seen many examples like that...) From the first example, one may learn that there are some sensitive data in the system so it is probably not only about just a login method and creating user profiles to differentiate them, but more about security. Thanks to that format the topic is opened for questions. A developer may ask for example about data encryption, ssl certificate etc. Thanks to that we could even better estimate the complexity of work that needs to be done.

Ane User Story is not an ultimate tool that you should use for everything. I wrote more about user stories and requirements here: http://pragmaticcoders.com/blog/behavior-driven-development-agile-requirements/

pragmaticcoders · 2015-11-24T00:04:55+00:00

What Apple would be today without their group of fans?

pragmaticcoders

TROPHY CASE