User Stories vs Requirements

When writing any specification of requirements and the product register and sprint register, non-functional requirements should be included in this specification. While the user’s story itself usually represents functional requirements, in my opinion a small problem is with non-functional requirements that represent system-level expectations. Lack of non-functional requirements or their insufficient quantity are often a …

User Stories vs Requirements Read More »

Implementation of the Methodology – Selection of a Modeling Tool

In many companies there is a discussion about formalizing the software development process. Spontaneous creation of diagrams by broadly understood analysts and designers does not build the value of documentation. The value is created when the whole team adds a diagram to the diagram as a brick to a brick. The added business process models …

Implementation of the Methodology – Selection of a Modeling Tool Read More »

Registration of Problems Identified During the Analysis

I received an interesting question by e-mail: According to your knowledge, is there an object in EA that would be best suited for registering problems identified during business or system analysis (AS-IS)? I mean an object in which the parameters of the problem identified during the workshop would be registered, e.g. name, description, connection to …

Registration of Problems Identified During the Analysis Read More »

Kanban Reports

Process management is a midway to success. The second midway is process monitoring and drawing conclusions. In Kanban, there are indicators, which enable process monitoring. They allow the team to improve the process. My favourite indicators are as follows: Delivery time – time for the entire flow Throughput – how many tasks are included in a …

Kanban Reports Read More »

Kanban Bottlenecks

Queues and WIP limits, which I discussed in the previous posts,  make up a chief indicator of problems in the flow. They show bottlenecks and when they are going to form. Bottlenecks are noticeable by an accumulation of work before them, and when in the queues after them there are no tasks. The board below …

Kanban Bottlenecks Read More »

Scroll to Top