Articles

7 Habitudes des Testeurs Efficaces

Actualités, Méthodes et organisation des process IT

Les testeurs efficaces ont des habitudes qui leur permettent d’atteindre leurs objectifs. Découvrez les 7 habitudes qui font la différence!

Les sept habitudes sont discutées dans cet article, qui les encadre pour des testeurs très réussis. Voici les sept habitudes :

Develop a plan of action for the project.

Create a database of the project’s requirements.

Make sure everyone on the team is aware of the project’s objectives.

Begin With the End in Mind

Before beginning a project, it is important to have a clear understanding of what the end result should be. This will help you to focus on the tasks that need to be completed in order to achieve the desired outcome. It is also important to consider the stakeholders involved in the project, as their expectations should be taken into account when creating the plan. Additionally, it is beneficial to create a timeline for the project and set deadlines for each task. This will help to ensure that the project is completed on time and within budget. Here are three suggestions for approaching upcoming undertakings with a clear goal in mind:

Create a list of objectives for the project.

Develop a timeline for the project.

Create a database of the project’s stakeholders.

Put First Things First

In order to ensure that a project is completed on time and within budget, it is important to prioritize tasks. This means that tasks that are most important should be completed first, while those that are less important should be completed last. It is also important to consider the resources available when prioritizing tasks. For example, if there are limited resources available, tasks that require those resources should be completed first. Here are three suggestions for approaching upcoming undertakings with prioritization in mind:

Create a list of tasks in order of importance.

Develop a timeline for the project.

Create a database of the project’s resources.

Les sept habitudes pour les testeurs très réussis

Cet article discute les sept habitudes qui sont nécessaires pour les testeurs très réussis. Ces sept habitudes sont :

Être Proactif

Commencer par la fin en tête

Mettre les choses importantes en premier

Penser Gagner/Gagner

Chercher à comprendre avant d’être compris

Synergiser

Aiguiser la scie

Être Proactif

Dans chaque projet de logiciel, l’objectif d’un testeur est de garantir qu’un produit de haute qualité est produit. Vous avez deux options lorsque vous déterminez ce qui s’est mal passé dans les projets de logiciels qui échouent en raison d’une qualité faible : vous pouvez être proactif ou réactif. Les personnes réactives ont tendance à attribuer des difficultés ou des obstacles aux autres personnes et aux facteurs externes. Être proactif vous permettra d’accepter la responsabilité des erreurs et de trouver des solutions pour les initiatives futures. Après la fin d’un projet, votre équipe devrait faire un « post-mortem » ou une « rétrospective » dans laquelle vous discutez franchement des succès et des échecs du projet. Voici trois suggestions pour aborder les prochaines entreprises avec initiative :

Élaborer un plan d’action pour le projet.

Créer une base de données des exigences du projet.

Assurez-vous que tous les membres de l’équipe sont conscients des objectifs du projet.

Commencer par la fin en tête

Avant de commencer un projet, il est important

Source de l’article sur DZONE

7 octobre 2023/par Service comm.

CockroachDB TIL : Vol. 12

Actualités, Méthodes et organisation des process IT

Découvrez le dernier volume de CockroachDB TIL ! Apprenez-en plus sur les fonctionnalités et les améliorations de CockroachDB pour vous aider à développer des applications plus robustes.

Articles précédents

Volumes 1 à 11

Sujets

Le volume 1 à 11 de cet article traite de différents sujets liés au logiciel. Dans ce volume, nous allons examiner le sujet n°1 : Identifier les index partiels. Notre équipe d’ingénieurs a publié un avis technique #96924 indiquant que certains changements de schéma, tels que la suppression de colonnes référencées dans des index partiels, échoueront. Un client demande comment identifier les bases de données, les tables et les index partiels associés qui référencent les colonnes à supprimer. Les méthodes suivantes vont aider à trouver ces index indésirables.

En considérant une table avec les données suivantes :

Table: customers

Columns: id, name, address

Indexes:

CREATE INDEX customers_name_idx ON customers (name) WHERE address IS NOT NULL;

CREATE INDEX customers_address_idx ON customers (address) WHERE name IS NOT NULL;

La première méthode consiste à exécuter une requête SQL pour obtenir les informations sur les index partiels. La requête suivante peut être utilisée pour obtenir les informations sur les index partiels pour la table « customers » :

SELECT * FROM pg_indexes WHERE indpred IS NOT NULL AND tablename = ‘customers’;

Cette requête renvoie les informations sur les index partiels pour la table « customers ». Le résultat de cette requête est le suivant :

indexname | tablename | indpred

———-+———–+———

customers_name_idx | customers | (address IS NOT NULL)

customers_address_idx | customers | (name IS NOT NULL)

La deuxième méthode consiste à utiliser un outil logiciel pour identifier les index partiels. Il existe plusieurs outils logiciels qui peuvent être utilisés pour identifier les index partiels. Certains des outils logiciels populaires sont pg_indexes, pg_stat_user_indexes et pg_stat_all_indexes. Ces outils peuvent être utilisés pour obtenir des informations détaillées sur les index partiels d’une base de données. Ces outils peuvent également être utilisés pour obtenir des informations sur les index partiels pour une table spécifique.

Enfin, la troisième méthode consiste à utiliser le fichier de configuration du serveur PostgreSQL pour identifier les index partiels. Le fichier de configuration du serveur PostgreSQL contient des informations détaillées sur les index partiels. Ces informations peuvent être utilisées pour identifier les index partiels pour une base de données ou une table spécifique.

En conclusion, il existe plusieurs méthodes pour identifier les index partiels dans une base de données PostgreSQL. Ces méthodes peuvent être utilisées pour obtenir des informations détaillées sur les index partiels d’une base de données ou d’une table spécifique. Ces méthodes peuvent également être utilisées pour identifier les index partiels qui référencent des colonnes à supprimer.

Source de l’article sur DZONE

21 avril 2023/par Service comm.

Should You Invest in a Digital Transformation Office?

Actualités, Méthodes et organisation des process IT

Undertaking a digital transformation journey is easier said than done. Efforts to transform an organization often face significant challenges, including integration of legacy platforms with modern technology stacks, the skill sets required for implementation, and an organizational structure that can communicate and embrace change. According to a 2020 study by the Boston Group, 72% of digital transformations fail, falling short of their objectives, and are often met with radical consequences after.

With so much at stake when it comes to transforming an organization, Adecco Group’s Sabine Laute suggests that a dedicated transformation office could be a viable solution.

Source de l’article sur DZONE

20 juillet 2022/par Service comm.

10 Dos and Don’Ts of Web Design in 2022

Actualités, Actualités

Navigating the world of web design can be difficult. There is so much conflicting and outdated advice.

How many times have you been advised to obey the 3-Click Rule? It states that users must reach the content they want in three clicks. But, according to the Nielsen Norman Group, no research supports the 3-Click Rule. It’s just a guess, the web’s equivalent of an urban myth.

There are dos and don’ts of effective web design in 2022. In this post, we’ll present the most important so that you can design websites with confidence.

Do: Make Use of Design Patterns

Design Patterns sound like a complex technique. All it means is copying standard, well-known approaches. Jakob’s Law says that most people spend most of their time on other sites, so they will understand your site better if it is like those other sites.

You can’t make your site like every other, so your job is to pick and choose which design patterns will be most helpful to your target demographic.

Some of the most recognized design patterns include placing the logo in the top left of the viewport, underlining links, and placing essentials like shipping information in the footer.

Do: Make It Inclusive

Inclusive design holds the opinion that the web is for everybody. It hasn’t always been that way. Just a few years ago, it was common to see sites excluding some demographics to reduce development costs.

Excluding anyone from your website is wrong. In many jurisdictions, it’s so wrong it’s illegal. But, perhaps more importantly, excluding 5% of users deducts 5% from your profits.

It’s never been easier to be inclusive. The first step is to make your website responsive so that it caters to every device. Then, follow accessibility guidelines to ensure that you welcome everyone. Finally, be ready to listen to your users, and adapt to their needs.

Do: Keep It Simple

As a website designer, you’ve undoubtedly looked in envy at some of the more original sites out there. It’s important to remember that many of the most experimental sites are usually targeting other designers. Something that works well on a portfolio site won’t translate well to a local convenience store.

99 times out of 100, the simple choice is the right choice. Most people aren’t interested in an original design. They’re interested in accomplishing a task. The less effort expended to complete the task, the better the experience.

Complexity most often creeps into navigation. Start with a logical structure, and use simple, hierarchical navigation.

Do: Stay Focussed

Every website has goals. It might be promotion, profit, utility, or a combination. Each part of that website, every single page, should have one goal.

Hick’s Law says that the time it takes to make a decision increases when there are more choices. And the Goal-Gradient Effect says that a customer is more likely to complete a process the closer they are to the completion. Combine the two, and it means that giving users one CTA (call to action) on a page increases the chances of them taking it.

It’s OK to still have navigation, links, and secondary goals provided each page has a single clear purpose.

Do: Keep Your UI Consistent

Consistency is often referred to as the hallmark of quality. It means that you’ve paid attention to details. But consistency isn’t just about giving a good impression. Consistency is also essential for good UX (user experience).

Users learn to navigate your website as they go. They learn your website’s ‘rules’ or the logic as they interact with it. If your UI (user interface) is consistent, they’ll learn the rules faster and feel more confident.

Areas that often fail the consistency test are the corner radius of boxes, the style of links, and the tone of writing.

Don’t: Ignore Aesthetics

Design isn’t all about usability studies and reliance on design patterns. Design should also be beautiful.

Beauty is often seen as shallow and unimportant. However, the Aesthetic-Usability Effect states that a beautiful website is more likely to be seen as usable by customers.

A pretty design is a high-converting design.

To ensure your design is pretty, pay attention to your typography hierarchy, color scheme, and the symmetry of your layout.

Don’t: Make Users Wait

The worst thing you can do is make users wait. The more technology advances, the faster connections get the higher user expectations.

Your site needs to load in under a second and be interactive in under two seconds. Otherwise, you’ll lose customers who bounce back to their search engine and try one of your competitors instead.

Delays don’t only apply to the speed of your site. You need to ensure that the information or product a customer wants is easy to access. Don’t bury it multiple levels deep in your site. If users are delayed by complicated navigation or unpredictable structure, they will exit your site as surely as if it took 10 seconds to load.

Users have zero amounts of patience.

Don’t: Block the Screen

Browsing through the web, the number of designers that block users from seeing the content on a website is astounding.

The most common culprits are newsletter subscription offers. How can a customer know whether they want to sign up for your newsletter when they haven’t yet seen your products?! Let the user browse your site, and then offer them a newsletter subscription.

Another common culprit is cookie notices. Most sites require a modest cookie notice to stay on the right side of the Law. And yet they display a huge, site-blocking modal as if the cookie notice were the most critical content on the site.

Don’t: Leave Content Until Last

Content is frequently left until last. That’s because it’s hard. Just because we learned to read and write as kids doesn’t mean we can write persuasive, engaging sales copy.

Content is vitally important for SEO (search engine optimization), but more importantly, it’s essential for CX (customer experience).

Most websites make three big mistakes with their content.

Mistake one is unbalanced copy. That means writing 25 words about your flagship product and 5,000 words about the company’s history.

Mistake two is writing for the company, not for the customer. That means organizing content around the company structure rather than customer tasks.

Mistake three is too much content at once. Walls of text are a turn-off. Instead, write short, scannable snippets that will keep customers engaged.

“Don’t try to be original…

…Just try to be good.”

That quote is from the titan of twentieth-century design, Paul Rand.

It boils down to this: originality is about you, and quality is about the website. Great designers care more about their output than their reputation.

Featured image via Pexels.

Source

The post 10 Dos and Don’Ts of Web Design in 2022 first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

10 juin 2022/par Service comm.

A Brief History of Responsive Web Design

Actualités, Actualités

Websites haven’t always been as adaptable as they are today. For modern designers, “responsivity” is one of the most significant defining factors of a good design. After all, we’re now catering to a host of users who frequently jump between mobile and desktop devices with varying screen sizes.

However, the shift to responsive design didn’t happen overnight. For years, we’ve been tweaking the concept of “responsive web design” to eventually reach the stage we’re at today.

Today, we’re going to take a closer look at the history of responsive web design.

Where Did Web Design Begin?

When the first websites were initially created, no one was worried about responsivity across a range of screens. All sites were designed to fit the same templates, and developers didn’t spend a lot of time on concepts like design, layout, and typography.

Even when the wider adoption of CSS technology began, most developers didn’t have to worry much about adapting content to different screen sizes. However, they still found a few ways to work with different monitor and browser sizes.

Liquid Layouts

The main two layout options available to developers in the early days were fixed-width, or liquid layout.

With fixed-width layouts, the design was more likely to break if your monitor wasn’t the exact same resolution as the one the site was designed on. You can see an example here.

Alternatively, liquid layouts, coined by Glenn Davis, were considered one of the first revolutionary examples of responsive web design.

Liquid layouts could adapt to different monitor resolutions and browser sizes. However, content could also overflow, and text would frequently break on smaller screens.

Resolution-Dependent Layouts

In 2004, a blog post by Cameron Adams introduced a new method of using JavaScript to swap out stylesheets based on a browser window size. This technique became known as “resolution-dependent layouts”. Even though they required more work from developers, resolution-dependent layouts allowed for more fine-grained control over the site’s design.

The resolution-dependent layout basically functioned as an early version of CSS breakpoints, before they were a thing. The downside was developers had to create different stylesheets for each target resolution and ensure JavaScript worked across all browsers.

With so many browsers to consider at the time, jQuery became increasingly popular as a way to abstract the differences between browser options away.

The Rise of Mobile Subdomains

The introduction of concepts like resolution-dependent designs was happening at about the same time when many mobile devices were becoming more internet-enabled. Companies were creating browsers for their smartphones, and developers suddenly needed to account for these too.

Though mobile subdomains aimed to offer users the exact same functions they’d get from a desktop site on a smartphone, they were entirely separate applications.

Having a mobile subdomain, though complex, did have some benefits, such as allowing developers to specifically target SEO to mobile devices, and drive more traffic to mobile site variations. However, at the same time, developers then needed to manage two variations of the same website.

Back at the time when Apple had only just introduced its first iPad, countless web designers were still reliant on this old-fashioned and clunky strategy for enabling access to a website on every device. In the late 2000s, developers were often reliant on a number of tricks to make mobile sites more accessible. For instance, even simple layouts used the max-width: 100% trick for flexible images.

Fortunately, everything began to change when Ethan Marcotte coined the term “Responsive Web Design” on A List Apart. This article drew attention to John Allsopp’s exploration of web design architectural principles, and paved the way for all-in-one websites, capable of performing just as well on any device.

A New Age of Responsive Web Design

Marcotte’s article introduced three crucial components developers would need to consider when creating a responsive website: fluid grids, media queries, and flexible images.

Fluid Grids

The concept of fluid grids introduced the idea that websites should be able to adopt a variety of flexible columns that grow or shrink depending on the current size of the screen.

On mobile devices, this meant introducing one or two flexible content columns, while desktop devices could usually show more columns (due to greater space).

Flexible Images

Flexible images introduced the idea that, like content, images should be able to grow or shrink alongside the fluid grid they’re located in. As mentioned above, previously, developers used something called the “max-width” trick to enable this.

If you were holding an image in a container, then it could easily overflow, particularly if the container was responsive. However, if you set the “max-width” to 100%, the image just resizes with its parent container.

Media Queries

The idea of “media queries” referred to the CSS media queries, introduced in 2010 but not widely adopted until officially released as a W3 recommendation 2 years later. Media queries are essentially CSS rules triggered based on options like media type (print, screen, etc), and media features (height, width, etc).

Though they were simpler at the time, these queries allowed developers to essentially implement a simple kind of breakpoint – the kind of tools used in responsive design today. Breakpoints refer to when websites change their layout or style based on the browser window or device width.

Viewport Meta tags need to be used in most cases to ensure media queries work in the way today’s developers expect.

The Rise of Mobile-First Design

Since Marcotte’s introduction of Responsive Web Design, developers have been working on new ways to implement the idea as effectively as possible. Most developers now split into two categories, based on whether they consider the needs of the desktop device user first, or the needs of the mobile device user. The trend is increasingly accelerating towards the latter.

When designing a website from scratch in an age of mobile-first browsing, most developers believe that mobile-first is the best option. Mobile designs are often much simpler, and more minimalist, which matches a lot of the trends of current web design.

Taking the mobile first route means assessing the needs of the website from a mobile perspective first. You’d write your styles normally, using breakpoints once you start creating desktop and tablet layouts. Alternatively, if you took the desktop-first approach, you would need to constantly adapt it to smaller devices with your breakpoint choices.

Exploring the Future of Responsive Web Design

Responsive web design still isn’t perfect. There are countless sites out there that still fail to deliver the same incredible experience across all devices. What’s more, new challenges continue to emerge all the time, like figuring out how to design for new devices like AR headsets and smartwatches.

However, it’s fair to say we’ve come a long way since the early days of web design.

Featured image via Pexels.

Source

The post A Brief History of Responsive Web Design first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

1 juin 2022/par Service comm.

Observability for Monitoring Microservices: Top 5 Tools

Actualités, Méthodes et organisation des process IT

With microservices architecture becoming the de facto standard for web applications now, effective debugging and anomaly detection calls for a system that is observable — which means, the internal state of an application can be inferred by observing and tracking the metrics, traces, and logs.

Observability is all about data exposure and easy access to information required to find issues when the communications fail, internal events do not occur as expected or events occur when they shouldn’t. Here, you’ll learn and know about different microservices monitoring tools and how to monitor microservices. Let’s take a look!

Source de l’article sur DZONE

7 avril 2022/par Service comm.

7 Worst Fails in Email Marketing

Actualités, Actualités

The email channel is known for multiple advantages. It is convenient to implement practically, offers many options, and has a fantastic ROI of up to 4200%.

But we also face problems, the most disappointing of which is people ignore emails, not performing the desired action, or worst of all unsubscribing. Why does it happen?

The web is constantly progressing. It offers many tools like modern HTML template builders, ESP services, and other digital assistants that help us at all stages. But even the best tools are not enough; the secret of success still rests with us.

In this post we’ll cover the 7 cardinal sins of email marketing, to help you avoid them.

1. Being Too Late

I can define this mistake as probably the worst. It’s worse than broken links, incorrect dates, or prices. Even more harmful than ugly design.

We lose a lot when postponing email strategy implementation. Beginners often focus all their attention on the content, social media activities, SEO issues… All that is important, right. But ignoring email campaigns is a hard fail.

Thousands of visitors never come again to your website. In other words, they leave the very first levels of the marketing funnel. While regular emailing keeps them engaged and prevents churn.

So delays here are only profitable for competitors. Don’t wait until you collect “enough” contacts. Start as soon as possible.

Frequency matters too. Don’t bomb people with emails; it annoys and causes unsubscribes. Email frequency is an individual parameter depending on many factors.

2. Disregarding Clients’ Expectations

A fundamental axiom: people unsubscribe when emails are irrelevant. The same goes for neglected expectations. Even the best content with next-gen features won’t save the situation.

I mentioned the email frequency a bit above. Notice that if you announce the weekly emails but send them every day, this is an example of ignoring expectations. Be honest with readers.

Another typical issue is off-topic. If your subscribers are waiting for content related to smartphones, send them newsletters about smartphones, not dresses or domestic turtles :)

But in some cases, getting off-topic can be good. It all depends on the target audience, actual situation, and communication style.

3. Bad Segmentation

Once again, relevance is vital. So we must avoid generic emails. Instead, especially if your contact list is extensive enough, apply all the possible parameters: age, gender, location, customers history, etc.

Where to get the respective data? A typical solution is to use update preferences forms in emails or on the website. Let clients choose the topics that are interesting for them.

Use surveys, sign-in forms, AI-based techniques of segmentation… Smart algorithms are great helpers that track clients’ behavior and then process the data for segmentation purposes.

The better we know our subscribers, the deeper we segment the contact list. It allows sending precisely targeted newsletters to respective segments.

4. Insufficient Personalization

As Hubspot stats say, personalized emails’ open rate is 26% higher, and their click-through rate is 14% better. But even besides index data, poor personalization is just nonsense today.

Clients are looking for content that matches their preferences, so marketers have to consider these expectations. Segmentation and dynamic range are essential here, but they are not the only techniques.

Everything is much more sophisticated here, in addition to personalized subjects and content. Another solution is to generate recommendations that include the previously browsed products.

AI-powered automation comes to help. Machines will upgrade the classical personalization to the next level called hyper-personalization.

5. Underestimating Mobile-Friendliness

It’s simply unacceptable to send non-responsive emails today. With so many people opening email on different devices, this is a huge fail.

The modern world is full of gadgets and devices. Email has been opened on smartphones more frequently than on desktop PCs and notebooks in recent years. Up to 70% of readers will read messages on mobiles very soon. No wonder that responsivity turned into a mobile priority.

Regarding layout and design, there are no problems: modern template editors are featured with automated responsivity. But mobile-first means not only layout/design adjustment for mobiles, full-width buttons, or larger fonts. We have to work with content too. Don’t overwrite text remember that recipients read inbox emails on the run.

Just imagine yourself reading emails in the cafe or cab. And ask yourself: is everything convenient? Would you take the desired action on the run?

6. Non-Professional Approach

People are quite skeptical of new brands. We need to do our best to attract them. So everything must be done professionally.

The best solution: be a perfectionist. If newsletters look amateurish, they are likely to repel.

Being amateurish will also ruin your brand identity and reduce customers’ trust. Pay close attention to design, stick to your corporate style, analyze each detail in the context of overall harmony.

7. Overlooking Tests and Improvements

Testing is vital. Before sending an email campaign, check it via Litmus or Email on Acid to be sure that message looks just as planned. These tools allow testing email rendering by +90 combinations of email clients, devices, and OS.

Knowledge is power. Always try and test your marketing strategies. Are you satisfied with your actual performance? Run A/B tests and focus on the most significant wins and failures.

Summing Up

Of course, threats are not limited to these seven failures. The last piece of advice: never ignore trends.

Accessibility? Don’t forget about clients with special requirements. Get whitelisted and incorporate these technologies in your campaigns.

And constantly strive for perfection. With this doctrine, you’ll win!

Featured image via Pexels.

Source

The post 7 Worst Fails in Email Marketing first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

23 février 2022/par Service comm.

How to Get Started with the MVP Workflow

Actualités, Actualités

Few things are more important to a web designer or developer’s chances of success than having the proper workflow. The term “workflow” applies to the set of standardized steps you or your company uses to create, test, and deploy designs or products.

Over the years, as development processes have evolved, so too have the workflows experts use to bring their ideas to life. The MVP workflow, or “Minimum Viable Product” strategy, is one of the most popular options in 2022.

Here’s what you need to know about the MVP workflow and how it differs from some of the other standard workflows developers may be used to.

What is the Designer/Developer Workflow?

As mentioned above, the designer/developer workflow is a series of steps used by experts in the web design world to achieve a creative goal. The process includes the steps taken to start a project, evolve it, and finish it. Since software is never developed without tools, the technology you’ll access throughout the development process is also considered in most workflows.

An example of a standard development workflow might look like this:

Scaffolding: This is the stage wherein you start your new web project, creating a git repo, downloading libraries, preparing file structures, and completing other tasks to make sure your product is ready to roll out into the world.
Develop: This is where you’ll spend most of your time writing code for your application or website. The development process may include various specific tools and support from other staff members.
Test: In this stage, you examine the functionality of your code to determine if everything works as it should. If there are errors or issues, you can go back and develop fixes to the potential problems. Your code may go through the development/test process several times before you can move to the next stage.
Integrate: This is when you merge the code for your part of the development process with the rest of the team. You can also integrate your code into websites and existing apps at this point. If you’re working solo, you can skip this process.
Optimize: You prepare all your assets for use on a production server during the optimization stage. Files are generally optimized to ensure your visitors can view your site easily or access your applications with ease.
Deploy: In the deployment stage, developers push code and assets up into the server and allow for changes to be viewed by the public.

What is MVP? (Minimum Viable Product)

Now you know what a developer workflow looks like, you can begin to assess the concept of the “MVP” workflow. The term “MVP” stands for Minimum Viable Product.

The idea of “Minimum Viable Product” applies to a range of industries, from education to healthcare and government entities. This term comes from lean start-up practices and focuses heavily on the value of learning and changing during the development process.

When you adapt your workflow to focus on an MVP, you’re essentially adjusting your focus to a point where you can create a stripped-back version of something new – like an app or a website. The MVP is built just with the core features (the minimum), so you can bring the idea to market and test it as quickly as possible.

For instance, if your goal were to create an attractive new website for a client, an MVP would focus on implementing the crucial initial tools, and nothing else. While you may create checkout pages, product pages, and other aspects of the site, you wouldn’t populate it with content or start experimenting with bonus widgets and apps.

So, how does this offer a better alternative to the standard workflow?

Simply put, an MVP workflow is quick, agile, and easy. The idea is you can validate key concepts with speed, fail quickly, and learn just as fast. Rather than having to build an entire app and almost start over from scratch every time you find an error, you can race through the iteration and development process.

MVP workflows are also highly appealing to start-ups and entrepreneurs hoping to validate ideas without a massive amount of upfront investment.

Examples of MVP Workflows

Still confused? The easiest way to understand how an MVP workflow works is to look at an example.

Let’s start with a conceptual example. Say you were building a voice transcription service for businesses. The desired features of this product might include the ability to download transcription, translate them into different languages, and integrate them into AI analytics tools.

However, using the MVP approach, you wouldn’t try to accomplish all of your goals with your software at once. Instead, you’d focus on something simple first – like the ability to download the transcripts. Once you confirm you can do that, you can start a new workflow for the next most important feature for the app.

One excellent example of a company with an MVP approach is Airbnb. The entrepreneurs behind this unicorn company, Joe Gebbia and Brian Chesky, didn’t have a lot of cash to build a business with at first. They had to use their own apartment to validate the idea of creating a website where people could share their available “space” in a home or apartment with the public.

To begin, Airbnb only created a very basic website, published photos of their property, and waited to see the results. After discovering people were genuinely interested in renting another person’s home, the company was able to begin experimenting with new ideas to make a site where people could list their properties for travelers.

The Pros and Cons of an MVP Workflow

There are a lot of benefits to the MVP workflow – particularly when it comes to gaining agility and developing new products quickly. However, there are downsides too.

Pros

With an MVP approach, you can maximize your learning opportunities and create a more innovative, successful product at speed. You get to test every step of the way.
You release iterations or versions of your product quickly, which means you discover problems faster, allowing you to quickly solve these issues.
You build on the benefits of customer fans, “evangelists” in the marketplace who are keen to help your product or service grow.
An MVP gives you more freedom to try out unique ideas and “risks” you might otherwise avoid with a traditional workflow.
Because you’re focusing on creating only the “minimum viable product,” you don’t have to spend a fortune on initially setting up your workflows.

Cons

Agile work with an MVP flow requires a lot of effort in collecting constant feedback from customers and releasing iterations.
You’ll need to dedicate yourself to releasing many small and frequent product releases on a tight schedule.
You might have to revise the functionality of your product or app a number of times.

Creating Your MVP Workflow

If you believe an MVP workflow might be effective for you, the first step is defining your “Minimum Viable Product.” The app, website, or product you design needs to align with your team’s strategic goals, so think about what your company is trying to achieve at this moment – before you get started. If you have limited resources, or specific purposes, like improving your reputation as a reliable company, now might not be the right time to develop a new MVP.

Ask what purpose your minimum viable product will serve and what kind of market you’re going to be targeting. You’ll need to know your target customer to help you test the quality and performance of each iteration of your MVP. Once you know what your ideal “product” is, ask yourself what the most important features will be.

You can base these decisions on things like:

User research
Competitive analysis
Feedback from your audience

For example, if you’re producing an AI chatbot that helps companies to sort through customer inquiries, the most important “initial feature” may be the ability to integrate that bot into existing websites and apps owned by the company.

MVP Approach Guidelines

Once you have your hierarchy of most valuable features for your minimum viable product, you can translate this into an action plan for development. Remember, although you’re focusing on the “minimum” in development, your product still needs to be “viable.” In other words, it still needs to allow your customer to achieve a specific goal.

Review your features: Reviewing your prioritized product requirements and the minimum level of functionality you can deliver with each of these “features.” You need to ensure you’re still providing value to your customer with anything you produce.
Build your solution: Build your minimum set of features for the product or service. Remember to build only what is required. You can use methodologies like the agile or waterfall method to help guide your team during this process.
Validate your solution: Release your offering into the market, and ensure you have tools in place to gather feedback from early adopters. Use beta programs, focus groups, and market interviews to understand how your solution works for your customers and where you can improve on your current offer.
Release new iterations: Based on what you learn from your target audience, release improvements to your product quickly. Use your validation strategies to collect information from your audience with each release.
Review again: Go back to your product requirements and desired features and start the process over again, this time focusing on the next most valuable functionality. Over time, the value of your minimum viable product will increase.

Using the MVP Workflow Approach

While the MVP workflow approach might not be the right solution for every development or design team, it can work very effectively in the right circumstances. The MVP approach doesn’t minimize the importance of understanding market problems and delivering value. Instead, the focus is on delivering quick value that gradually increases and evolves over time.

As many developers and designers know, the most useful form of product validation in most cases is real-world validation. When your customers have had an opportunity to use a product on a day-to-day basis, they can provide much more effective feedback.

Just keep in mind that committing to the MVP approach also means changing your workflow and committing to iterations – otherwise, other features may never be completed. You’ll need to be willing to work quickly and in small bursts without getting too heavily caught up in one feature or functionality.

Featured image via Pexels.

Source

The post How to Get Started with the MVP Workflow first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

20 janvier 2022/par Service comm.