Simplicity

How to prototype in IT system development

Krzysztof Liszewski
Simplicity
August 10, 2020August 10, 2020

Some time ago I had a very fruitful retrospective session with a team which I support. It was about approach to prototyping. We created a “prototyping contract” – a set of general rules that we would like to follow while… Read More »

MDA framework for IT system design

Krzysztof Liszewski
Simplicity
May 5, 2020May 5, 2020

In my free time, I play boardgames quite a lot. To be honest not only play, but also read about them, analyse and try to design new ones. Some time ago I have discovered the MDA framework – formal approach… Read More »

User Story defined in 3 acronyms

Krzysztof Liszewski
Simplicity
August 21, 2019August 21, 2019

User Story is one of the most popular form of requirements documentation in Agile projects. Each User Story contains all needed for proper requirement description: who, what and why. As a <role> I would like to <what> in order to… Read More »

To re-estimate, or not to re-estimate?

Krzysztof Liszewski
Simplicity
July 30, 2019November 10, 2020
5 Comments

That is the question. In practice it is quite rare to deliver hundred percent of the Sprint Backlog. In most cases when the Sprint ends there are still some Items left undone – those that do not fully meet your… Read More »

How to manage technical debt

Krzysztof Liszewski
Change, Simplicity
July 3, 2019September 22, 2019

Let’s talk a bit about technical debt. There will be some theory, but I hope this article won’t be against my Manifesto. I’m still aiming to give you practical tools for discussion and to explain why and how to manage… Read More »

Quality vs quantity

Krzysztof Liszewski
Change, Simplicity
June 16, 2019September 22, 2019

Let’s talk a bit about: quality vs quantity? I’ll anchor this debate in Scrum – so the main actors will be Product Owner and Development Team – however the same would apply to any other Agile framework. Imagine there are… Read More »