We are currently in a “strange situation”. There are user stores and usage case scenarios, of which the latter can be divided into formal and informal use cases as well as summaries of use cases. What are they different and what are they the same? Use cases, usage case scenarios and user stories document the …
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 …
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 »
It is impossible to hide that working on Enterprise Architect is sometimes quite a challenge. Especially the publication of diagrams is a big problem. Not without a reason, I also published a special course, which tells how to report with Enterprise Architect. I think that this situation is changing for the better. Already over a …
Enterprise Architect Pro Cloud Server – Modeling in the Cloud Read More »
Software development is a process in which the reviews of the status of work are a daily or almost everyday situation. Verification of analytical and design works as well as architectural works is not only a question of what has been done, but also questions: how has it been done? How will it work? In …
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 »
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 …
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 …
For some time, there has been a discussion about the value of modeling. Advocates of agile approach are not very happy to see models. Conservatives preferring the classic approach to the software development process are more likely to model. Modeling costs. The tools are usually not much, but people (analysts, designers, architects) have a lot. …
In the preceding Kanban post, I wrote about partially done work. I wrote that it is worth limiting partily done work. The WIP (Work In Progress) which is too high results in the fact that some work is not performed, and the WIP which is too low causes that some people are without work. It …
