Welcome to Ed2Ti Blog.

My journey on IT is here.

A few years ago, I did a POS for a small company using Delphi, PHP, and MySql. It was a simple project to attend just one store and no max than 10 lanes (cashiers). In this old project, I developed the main software in Delphi (with a local paradox database) accessing a centralized database with a Mysql server. All the routines to manage the store I did in PHP, accessing the MySql Server.

The images used were stored in a Microsoft Samba driver and all new products (images) are updated on the lanes using this Samba file share. When we are talking about a small company, with good network access control, It works very well.

You may be curious if this software continues working until now. The answer is: No. After 2 years the company closed the doors and I did not continue this project. (I tried to find the code, but I don't have it anymore)

Today I'll refactor this old project into a new one, but now I'll use the Well-Architected. In this new project, we have:

  1. Point Of Sale - I'll do everything in Delphi 11 - Community Edition with sqlight3;
  2. StoreGateKeeper - I'll do It in GoLang with PostgreSQL;
  3. StoreManager - I'll do It in Laravel with PostgreSQL;

The StoreManager will be a centralized solution hosted in Cloud (Azure).

Details about this project and all codes you may get at my GiT: https://github.com/ed2ti/POS-Well-Architected

Here is the first diagram from this project.

enter image description here

A few days ago I was with a friend talking about technology, and he told me about Agile Methodology. He told me that all projects can be managed using agile methodology with Scrum. Of course, I stayed listening for a long time. In the end, I asked a simple question: What kind of project are you talking about?

We know that a project delivers a unique product or service that has a start and end date. [very good to start]

Why is so important to understand the kind of project we will manage to decide the best methodology? For some projects, like the building of a bridge, is important to map all the requirements before we start the project. In this case, normally we do not change the project during the execution. In this case, we need to define a budget before we start it. In this case, is better to use traditional methodology.

But, if we are talking about software projects, it may be a little bit different.

What we really have before we start the project:

  • The customer never has all the ideas in mind;
  • The ideas are not enough clear;
  • The environment may change.

We need to be capable of adjusting our direction quickly. In my opinion, the Agile team accepts the changes with more resignation.

The project manager needs to understand the project objectives and all the environments around the project to decide the best methodology.

This weekend I was thinking about a colleague with whom I tried to do a meeting and I desisted. When I saw his schedule he just had time between 13:00 and 13:30.

This hour, I imagined, he may be having lunch.

I don't want to judge anyone, but if I have the freedom to talk with him, I will give some advice: You don't need a full scheduler (all the time occupied) to show that you are working.

In my opinion, if you are every day and every time at meetings, you will never have time to produce.

I'm not saying the meetings are not important, of course, they are, we just need to join exactly to the share and decision meetings. Many meetings just need a simple "ok"

I encourage you to try new horizons. After some years working with IT, I have never been deep in "Software Test" knowledge. Now I'll share this new journey. We need to link all our background technologies to deliver the most performative and professional solutions.

a) Agile Test Foundation

I'll update this post with all my ISTQB certifications.

There are many benefits to organizations, including the ability to quantitatively measure progress and performance, maintain a strategic focus on critical objectives, make informed and data-driven decisions, proactively identify issues, foster accountability and motivation among teams, benchmark against industry standards, optimize resource allocation, drive continuous improvement, enhance communication and alignment, and ensure the financial health and risk management of the organization, making them invaluable tools for achieving strategic goals and maintaining competitiveness.

The benefits of Key Performance Indicators (KPIs) for businesses and organizations.

  1. Performance Measurement:

    KPIs provide a structured and quantitative way to measure performance. Instead of relying on vague or subjective assessments, organizations can use specific metrics to gauge how well they're doing. This clarity is especially valuable when evaluating complex aspects of business performance, such as customer satisfaction, employee engagement, or product quality.

  2. Strategic Alignment:

    KPIs are directly linked to an organization's strategic objectives and goals. This alignment ensures that everyone within the organization is focused on achieving the same priorities. It helps prevent "mission drift," where efforts become scattered and less effective.

  3. Data-Driven Decision-Making:

    KPIs are grounded in data and facts. This data-driven approach enables better decision-making across all levels of the organization. Leaders can analyze KPI trends, identify areas of improvement or concern, and make informed choices about resource allocation, process changes, and strategic shifts.

  4. Early Problem Detection:

    KPIs act as early warning systems. When certain metrics deviate from their targets, it signals potential issues that may need immediate attention. This proactive approach allows organizations to address problems before they escalate and impact overall performance.

  5. Accountability and Responsibility:

    KPIs assign clear accountability for specific results. Individuals, teams, or departments responsible for achieving particular KPIs are more likely to take ownership of their performance areas. This accountability fosters a culture of responsibility and can drive better outcomes.

  6. Motivation and Engagement:

    Well-defined KPIs can be motivational tools. When employees have clear goals and can see their progress toward those goals, it can boost morale and engagement. Achieving KPIs can provide a sense of accomplishment and purpose in their work.

  7. Benchmarking and Competition:

    KPIs allow organizations to benchmark their performance against industry standards, competitors, or their own historical data. This benchmarking process helps identify areas where they excel, enabling them to capitalize on strengths, and areas that need improvement, guiding strategies for growth.

  8. Optimized Resource Allocation:

    By monitoring KPIs, organizations can make data-driven decisions about where to allocate their resources. They can identify areas that are performing well and may deserve additional investment. Conversely, they can identify areas where resources can be optimized or redirected for better results.

  9. Continuous Improvement:

    KPIs are a central component of a continuous improvement culture. Regularly reviewing and analyzing KPI data allows organizations to identify opportunities for enhancement and implement changes to achieve better results over time.

  10. Communication and Alignment:

    KPIs provide a common language for communication within an organization. They ensure that everyone understands the strategic priorities and can align their efforts accordingly. This alignment fosters teamwork and synergy, as everyone works toward common goals.

In conclusion, Key Performance Indicators are invaluable tools that offer numerous benefits to organizations. They help measure, align, and improve performance, leading to better decision-making, enhanced productivity, and ultimately, greater success in achieving strategic objectives. The ability to monitor and manage performance through KPIs is a cornerstone of modern business management.