Advisory Services

Tom Burger is a specialist in the field of software architecture & design and strategic software development. Amsterdam is his hometown.

Software Architecture & Design: Agile Software

Organizations often claim they are Agile but forget that the software should be agile. Agile software is software that can easily be transformed to accommodate the always evolving business needs. If your organization encounters issues that development teams are pushing back on changes to the software, then they are most likely indicating that the software became [too] complex to alter. The engineering team was not able to adopt agility into their software.

A software assessment and software development training can turn this around, and restore your development velocity needed to succeed in your business.

Organization: Strategic Software Development

Strategic software development is focussed around structuring your technology organization so that your resources are working on realizing your future business opportunities. Too often, too many resources are spent into addressing only today's issues. The organization does want to move forward but is somehow paralyzed by this "firefighting". Luckily, there is a way out. This is a symptom of not having the right processes and team structure into place to control the balance between sustenance and strategic work. Introducing well-defined processes and improve team structure will resolve this issue.

An organizational assessment with an improvement plan can enable you to improve and mature your processes and organizational structure to control the resources spend on sustenance and allow you to work strategic development.

Contact

info@tvburger.net

See also his LinkedIn profile.

Comments

Post a Comment

Popular posts from this blog

Principles of Software Quality Management

Image
Poor Man's Approach To start the conversation, let's first examine a wide spread idea of quality management: Quality is a compromise between Scope, Resources and Schedule (The Iron Triangle of Projects); and, Bugs must be prioritized based on Impact and Likelihood. Based on a metaphor it shows why the above idea is a very limited and an impractical approach to software quality management, and it allows us to immediately make two conclusions: software development is a society and QA is the hospital in that society; people that get ill are sent to the hospital to get cured. Quality is non-negotiable: letting people die is always unacceptable; Prioritizing won't improve anything: it won't reduce the number of people getting ill. Principles of Software Quality Management Quality of software is measured through bugs. There is no known or set formula to quantify the software quality, but what is measured is number of bugs and this is the basis to imply the quality. T
Read more

Analyzing Software: Technical, Tactical and Strategic Qualities

Building software always comes with significant investments, but should be only a fraction of the possible long term gains. To ensure the software yields the expected outcomes, not only for the first releases, the first two years, but long term, the software must be developed with different qualities. Long term? How many systems does your organization have, that are 3+ years old and are not limiting the potential capabilities of the company [without reinvesting/rewriting them]?. In this article a small framework to assess the quality of your software is presented. To ensure software is profitable for the company during its full potential, we analyze the software on 3 different levels: Technical, Tactical and Strategic. This can be the first step to improve the earn backs of your technology/software investments. Technical Quality When people learn how to program, the syntax of the language is explained. Next in detail is explained, how to do recursion, with the termination conditi
Read more

External Services Integration Strategies

In today's world, the systems you are developing are not isolated, they need many different integrations with other external services. From Authentication Systems (using SAML, LDAP, OIDC) to Data and Processing Systems (Malware Analysis, CRMs, Ticketing Systems). Although the number of actual systems to integrate with is vast, luckily the Use Cases and types of integrations are manageable. Here we will discuss popular Use Cases and list integration strategies to accomplish them. Use Case 1: Transfer the User from your System to the External Service In this scenario, the User is working in your system and is now required to access specific functionality in an External Service. The following steps must happen: the service must be located, the user must be authenticated, and the right interface/data must be presented. 1.1 Service Locator Integration Your system understands how to find the specific service, the user does not need to remember the location of the external service
Read more