I recently read again the article Principles VS Methodology, by Javier Cañada, a reference for me. In this text, he explains how, for him, the methodology is in the background in favour of universal design principles.
He looks at it from a design point of view, but I can not agree more if we apply it also to the complete development of a product on the Internet: the methodology is only a means to obtain a result and must be subject to it.
This does not mean that methodology is unimportant. When you work as a team with a group of people, however senior you are, you need some sort of organisation and set some minimum work agreements.
That is why, inevitably, we need a methodology and, therefore, unlike Javier, I do continue to feel interested in this area, but seen from this point of view. I do not feel a fascination for the process itself, but I understand it as a means that allows you to bring greater value to the outcome of a project.
January 2007. While Steve Jobs and Apple were revolutionising the world with the introduction of the iPhone, we were taking our first steps. Thus was born Paradigma Tecnológico. It was just the beginning of a long and exhilarating road. Today, 10 years later, many things have changed, but some things, like the excitement, determination, and confidence, remain. We’ve turned 10 years old! This is our story.
Set the stage, Gather data, Generate insights, Decide what to do, Close the retrospective. These are the five steps that will help us make the most of our retrospective meetings.
Continuous improvement is one of the core values of agile project management and, to that end, retrospectives represent a moment of inspection and adaptation for our processes and teams. Nevertheless, we should not assume that retrospectives are meetings that can only be conducted within an agile environment.
Even if you’re working in projects with more traditional management, you should set aside a moment, from time to time, to sit down with your team and reflect on how things are being carried out.
At a time when the adoption of cloud technology seems unstoppable, when many companies are taking the plunge from virtualisation to a private cloud or to a public cloud, there are still doubts about if it is really secure.
Here we will analyse why we can eradicate once and for all this unfounded fear and begin to value cloud as the most secure option.
Over the past few days I have been reading and listening to quite a bit regarding the Digital Transformation, and how users are adapting to new technologies at a pace at which (still) very few companies can keep up. In fact, we at Paradigma like to say that the Digital Transformation means eliminating the barrier that stands between traditional companies and new digital clients.
I try to set examples for myself that go beyond a nice sentence to tell our clients, in order to confirm to myself that this is real. To set up the stage for these new digital clients, we usually make reference to our children, nephews and nieces, and how aptly they handle a Tablet, in order to show the way users are changing. But, often, these users still need a few years to become clients…
When I began to write this article, a few weeks ago, I talked about the amount of new frameworks, architectures and languages that come out every day, and about the need to separate the chaff from the wheat before investing our time in trying to assimilate new technologies.
I had crushed it, but on 17 May 2017, barely a week ago, Google announced that it was adopting Kotlin as a high-level language for Android development. In other words, the world has now been divided into those that shout ‘I knew it’ and those that whisper ‘but what does it mean?’.
I know that I’m asking you for an act of faith, but I can’t help but point out that at Paradigma we were on the side of the visionaries. So, without any more introduction, we’ll start with the most basic stuff…
The demands of market security in cloud environments are clear: the highest level of security possible for data and applications, compliance with all certifications and standards required and a clear and simple management that does not require investing much time.
To cover all these needs, the major cloud providers include all these tools on their platforms by default. In today’s post, we will see some of them.
Are you a mobile developer? Then the first decision that you will certainly make is which of the two mainstream platforms to begin with, iOS? Android? What does the final decision depend on? Among other things, on the previous knowledge that we have a priori or on the ability to adapt to new challenges.
Two of our developers are entering the arena to face these two platforms and to see what advantages and drawbacks developing in each operating system has. Let the battle begin!
The process of digital transformation isn’t straightforward, nor is it common practice, although it should be obligatory for all businesses that don’t want to lose their competitive edge in the the market. There is not magic recipe to guarantee successful digital transformation, not even between businesses in the same sector.
A company on its way towards digitalisation passes through different levels that allow it to achieve a degree of digital maturity. The difference between each of these levels isn’t linear, but exponential. A digital company is in the order of 1000 times more efficient than a traditional company. For this reason, digital native startups, despite having fewer resources available, are capable of competing with traditional businesses that are already well positioned in the market.
Based on years of experience helping large companies in their journey towards digital transformation, we have established four levels of maturity: beginner, intermediate, advanced, and expert.
Most analysts agree that we have been witnessing in the last few years the greatest disruption in IT that we have seen in twenty-five years, since the appearance of the Internet and customer/server architectures.
The convergence of technologies like Cloud (IaaS and PaaS), Big Data, Machine Learning, microservices, asynchronous architectures, API Management, etc. and methods such as Scrum, DevOps or continuous delivery allow for the development of digital products in ways that five or ten years ago, when companies like Google started using them, seemed nothing short of magic.
These new ways are radically changing the IT ecosystems of large companies all over the world. This is what we call velocity development. Facing this new technological train, many companies continue basing the core of their business on hosts with architecture and applications that are more than 30 years old. Many of them ask us if it is time to change and how to do it.