The winner is the topic about discovery😎
Let’s start.
So what is the Product discovery phase? In simple words, the Discovery phase is a part of the planning phase from PMBOK. It is strictly required to create a product roadmap and to make budget cost estimations.
The Discovery phase usually results in
Vision & Scope
Design Concept
Architecture Vision
Sometimes discovery phase can even result in avoiding spending millions on a product that is not worth it.
So let’s get a deeper understanding of what is a Discovery phase and what it consists of.
Product Discovery Phase Benefits
So let’s return to our skyscraper example. Just imagine you are building a skyscraper and when the 50-th floor is ready, you suddenly understand that you have forgotten about one additional entrance just because your plan has not been detailed enough?
Well, OK, in this case, you really can do nothing, and in software development, you actually can add one additional entry. But there is no such thing as a wonderland, it is going to cost the product team way more time and money than it might cost in case this entrance had been included in the preliminary plan.
The other problem is time to market, which is deadly important to any startup product.
Of course, the Agile approach to software development is the best way of managing product development, but in some cases, it can be quite dangerous. A lot of products fail because it is very easy to dive deep into details or fall into scope creep when all features seem to be so important. Agile is good, but don’t forget about clear and precise vision! Without that, time, effort and money are going to be lost.
So one of the main goals of any Discovery phase is to create such a vision and align the whole team with it.
#Discovery
Let’s start.
So what is the Product discovery phase? In simple words, the Discovery phase is a part of the planning phase from PMBOK. It is strictly required to create a product roadmap and to make budget cost estimations.
The Discovery phase usually results in
Vision & Scope
Design Concept
Architecture Vision
Sometimes discovery phase can even result in avoiding spending millions on a product that is not worth it.
So let’s get a deeper understanding of what is a Discovery phase and what it consists of.
Product Discovery Phase Benefits
So let’s return to our skyscraper example. Just imagine you are building a skyscraper and when the 50-th floor is ready, you suddenly understand that you have forgotten about one additional entrance just because your plan has not been detailed enough?
Well, OK, in this case, you really can do nothing, and in software development, you actually can add one additional entry. But there is no such thing as a wonderland, it is going to cost the product team way more time and money than it might cost in case this entrance had been included in the preliminary plan.
The other problem is time to market, which is deadly important to any startup product.
Of course, the Agile approach to software development is the best way of managing product development, but in some cases, it can be quite dangerous. A lot of products fail because it is very easy to dive deep into details or fall into scope creep when all features seem to be so important. Agile is good, but don’t forget about clear and precise vision! Without that, time, effort and money are going to be lost.
So one of the main goals of any Discovery phase is to create such a vision and align the whole team with it.
#Discovery
👍5🔥1
Let’s continue topic Discovery😎
Product Discovery Phase Challenges
So the Discovery phase is very useful, but it is also one of the toughest periods of any product's life.
First of all, you should understand your clients and their needs. When starting a new product you should always remember the first rule of a product owner: You are not your customer!
That means that everything should be tested. It is just like in science - everything you think your client wants is not a fact, it is just a hypothesis to test.
The second problem is creating the right ideas, and not missing anything important.
Identifying customers' problems is not easy itself, but it is just the beginning of the journey as at least 80% of success lies in the details of implementation.
And the third difficulty lies in discarding a lot of ideas that you like.The good thing is that you will be able to return to some of them later when your product will already be successful in the market. But at first, the product team must concentrate on just MVP scope to provide Customers with a “just enough” solution that will help them to deal with a problem that is important to them. And the Discovery phase is precisely the right time when you should understand the scope of your future MVP.
Product Discovery Steps
📎Understand your Customers, Market, and their key problems
You should start with a deep understanding of potential product Users and their problems which can be solved by using the product.
It is a strong starting point and even at this stage sometimes the whole product vision can be changed.
The key deliverable of the stage is User personas which are developed and included in the Vision and Scope document.
📎 Testing problems
Here we return to the main idea of hypothesis testing for the first time.
Cust dev methodology is far beyond this article's scope, but the main idea behind this is that your vision of potential customers' problems and their importance for customers is just a hypothesis that should be checked.
At the Customer discovery stage (as it is called in Cust Dev) you don’t propose solutions, but just ask your potential customers if they really do have problems you think they have and are they ready to pay for solving them.
The key deliverable at this phase is a product backlog which consists of user stories that are really important to your potential customers.
But sometimes this step can change the whole concept or even cause the discarding of the product idea.
At this stage, your potential customers help you in answering the following question: “What exactly are we going to create and Why?”
In the next episode we continue discussing other discovery steps⭐️
#Discovery
Product Discovery Phase Challenges
So the Discovery phase is very useful, but it is also one of the toughest periods of any product's life.
First of all, you should understand your clients and their needs. When starting a new product you should always remember the first rule of a product owner: You are not your customer!
That means that everything should be tested. It is just like in science - everything you think your client wants is not a fact, it is just a hypothesis to test.
The second problem is creating the right ideas, and not missing anything important.
Identifying customers' problems is not easy itself, but it is just the beginning of the journey as at least 80% of success lies in the details of implementation.
And the third difficulty lies in discarding a lot of ideas that you like.The good thing is that you will be able to return to some of them later when your product will already be successful in the market. But at first, the product team must concentrate on just MVP scope to provide Customers with a “just enough” solution that will help them to deal with a problem that is important to them. And the Discovery phase is precisely the right time when you should understand the scope of your future MVP.
Product Discovery Steps
📎Understand your Customers, Market, and their key problems
You should start with a deep understanding of potential product Users and their problems which can be solved by using the product.
It is a strong starting point and even at this stage sometimes the whole product vision can be changed.
The key deliverable of the stage is User personas which are developed and included in the Vision and Scope document.
📎 Testing problems
Here we return to the main idea of hypothesis testing for the first time.
Cust dev methodology is far beyond this article's scope, but the main idea behind this is that your vision of potential customers' problems and their importance for customers is just a hypothesis that should be checked.
At the Customer discovery stage (as it is called in Cust Dev) you don’t propose solutions, but just ask your potential customers if they really do have problems you think they have and are they ready to pay for solving them.
The key deliverable at this phase is a product backlog which consists of user stories that are really important to your potential customers.
But sometimes this step can change the whole concept or even cause the discarding of the product idea.
At this stage, your potential customers help you in answering the following question: “What exactly are we going to create and Why?”
In the next episode we continue discussing other discovery steps⭐️
#Discovery
👍8❤1🔥1
Let’s finish to discuss Discovery steps
📎 Proposing a solution
When we already know what you are going to build, you can start thinking about HOW should it be implemented. Two types of modeling should be done:
1. Functional
a. Use cases
b. Process diagrams
2. Object
a. Internal objects
b. Border objects
i. User interfaces
ii. Integrations
But don’t be afraid, at this stage we are doing just high-level modeling without diving deep into details. Our goal is to create “just enough” prototypes that will help us to explain to your potential customers how the product is going to work so that we will be able to test it.
📎 Testing solution
Now it is time to return to potential customers one more time! This time - with prototypes.
Testing solution (or Customer validation as it is called in Cust Dev methodology) includes testing your first prototypes with potential users.
In the discovery phase, we usually avoid writing even a line of code. Prototypes on this stage can even look like screens drawn on napkins, but usually, it is more serious prototypes created in InVision, Adobe XD or other similar tools.
And of course, it is an iterative process.
At this stage, it is very important to stop on time. When the concept is good enough the time comes to move further. You will always be able to further improve it when the product is already on market.
📎 Vision detailing and preliminary plan creation
My congratulations! Finally, you know WHAT you are going to create and HOW it is going to work.
So now the time has come to detail your vision and create a plan.
A good plan consists of
📌Vision and scope
📌Design concept
📌Technology stack
📌Architecture vision
📌Story map
📌Roadmap
📌Time and Budget estimates
📌Risk mitigation plan
Of course it should not be a detailed plan. It is just required to align the product team, detail MVP scope, and plan time-to-market. There is a lot of work to be done at the following stages, but at least, as the result of the discovery phase, you:
📍Can be sure that the product is worth doing
📍Have a clear vision of how is it going to look like
📍Have an understanding of how much time and money the product development is going to take.
👉Conclusion
As you can see, the discovery phase is one of the most important stages of any product lifecycle. Its main purposes are mitigating risks, shortening the time to market period, and saving a lot of time, nerve cells, and money.
#Discovery
📎 Proposing a solution
When we already know what you are going to build, you can start thinking about HOW should it be implemented. Two types of modeling should be done:
1. Functional
a. Use cases
b. Process diagrams
2. Object
a. Internal objects
b. Border objects
i. User interfaces
ii. Integrations
But don’t be afraid, at this stage we are doing just high-level modeling without diving deep into details. Our goal is to create “just enough” prototypes that will help us to explain to your potential customers how the product is going to work so that we will be able to test it.
📎 Testing solution
Now it is time to return to potential customers one more time! This time - with prototypes.
Testing solution (or Customer validation as it is called in Cust Dev methodology) includes testing your first prototypes with potential users.
In the discovery phase, we usually avoid writing even a line of code. Prototypes on this stage can even look like screens drawn on napkins, but usually, it is more serious prototypes created in InVision, Adobe XD or other similar tools.
And of course, it is an iterative process.
At this stage, it is very important to stop on time. When the concept is good enough the time comes to move further. You will always be able to further improve it when the product is already on market.
📎 Vision detailing and preliminary plan creation
My congratulations! Finally, you know WHAT you are going to create and HOW it is going to work.
So now the time has come to detail your vision and create a plan.
A good plan consists of
📌Vision and scope
📌Design concept
📌Technology stack
📌Architecture vision
📌Story map
📌Roadmap
📌Time and Budget estimates
📌Risk mitigation plan
Of course it should not be a detailed plan. It is just required to align the product team, detail MVP scope, and plan time-to-market. There is a lot of work to be done at the following stages, but at least, as the result of the discovery phase, you:
📍Can be sure that the product is worth doing
📍Have a clear vision of how is it going to look like
📍Have an understanding of how much time and money the product development is going to take.
👉Conclusion
As you can see, the discovery phase is one of the most important stages of any product lifecycle. Its main purposes are mitigating risks, shortening the time to market period, and saving a lot of time, nerve cells, and money.
#Discovery
👍5🔥2❤1
Scope creep and how to avoid it
Scope creep, also known as kitchen sink syndrome, is an issue of the uncontrolled changes or characteristics that had not been taken into account from the beginning of a project and are intended to be added to it.
Even if those changes are small, they can cause the project to take longer than planned and, therefore, be more expensive than originally stated.
👉Why it happens?
📎Lack of understanding: It can occur on the client or vendor’s side, when the stipulated agreements are not fully understood before the project begins.
📎No plan: By presenting your client with an outline of how the work will be carried out, you can avoid last-minute changes and save time by identifying what has been missed earlier.
📎Gold plating: This happens when the team adds features that the client did not request or that were not previously discussed.
👉How to avoid it?
📎Document everything.
There is nothing better than having everything written:
📌Documenting can protect both parties that the agreed requirements are met without missing something.
📌Provide transparent outlined plan and define project scope clear to you and the other stakeholders in the project.
📎Don't hesitate to ask.
In fact, this must be on both sides, since it is vital that you clearly know what the client's requirements are and that both agree on how it will be carried out.
Сommunication must be constant, clear and allow collaborative work. Therefore milestones will be planned wich will help to optimize the project as it progresses.
📎All changes have a price.
Make sure that the customer and the team takes this into account. Any, even a very small change, at first glance, may lead to extra costs and negatively affect project success.
To avoid constant and haphazard changes establish the change control process. Ask the requester to follow the process to suggest changes. And the most important don’t forget to review those requests with project participants to decide if it's worth changing the scope of the project
Scope creep, also known as kitchen sink syndrome, is an issue of the uncontrolled changes or characteristics that had not been taken into account from the beginning of a project and are intended to be added to it.
Even if those changes are small, they can cause the project to take longer than planned and, therefore, be more expensive than originally stated.
👉Why it happens?
📎Lack of understanding: It can occur on the client or vendor’s side, when the stipulated agreements are not fully understood before the project begins.
📎No plan: By presenting your client with an outline of how the work will be carried out, you can avoid last-minute changes and save time by identifying what has been missed earlier.
📎Gold plating: This happens when the team adds features that the client did not request or that were not previously discussed.
👉How to avoid it?
📎Document everything.
There is nothing better than having everything written:
📌Documenting can protect both parties that the agreed requirements are met without missing something.
📌Provide transparent outlined plan and define project scope clear to you and the other stakeholders in the project.
📎Don't hesitate to ask.
In fact, this must be on both sides, since it is vital that you clearly know what the client's requirements are and that both agree on how it will be carried out.
Сommunication must be constant, clear and allow collaborative work. Therefore milestones will be planned wich will help to optimize the project as it progresses.
📎All changes have a price.
Make sure that the customer and the team takes this into account. Any, even a very small change, at first glance, may lead to extra costs and negatively affect project success.
To avoid constant and haphazard changes establish the change control process. Ask the requester to follow the process to suggest changes. And the most important don’t forget to review those requests with project participants to decide if it's worth changing the scope of the project
👍9
The SWOT analysis is a widely used tool to determine the four most determining drivers of a company, a brand, a product or service or a campaign, among others.
These 4 drivers are: strengths, weaknesses, opportunities and threats.
With this analysis, it will be possible to identify the internal and external aspects that have the most impact, so that there is a clear vision that allows the development of future strategies to mitigate the risks and strengthen the positive aspects.
The SWOT analysis must be implemented at the beginning of a strategic planning process to have the most relevant and important aspects that indicate an approach to strategies to be applied. In a second phase, it is important to validate whether the factors indicated have changed in order to measure the effectiveness of the actions applied.
👉What should I take into account to carry out a SWOT analysis?
📌The template to be used to indicate the content for each of the forces is contemplated by a table divided into 4 boxes as follows:
📎Strengths
📎Opportunities
📎Weaknesses
📎Threats
📌Strengths
Place the internal factors of the organization, the product, the service, the brand or any other element to be analyzed. Here we answer question “what we do well?”.
📌Weaknesses.
In this box, point out the limitations of the existing processes, it can vary from the reduction of monetary funds to capacity deficiencies.
📌Opportunities.
Part, where we must identify areas where we have not ventured, alliances that have not been made but that have enough potential to become strengths.
📌Threats
Factors that cannot be directly controlled by you or your organization and that present themselves as obstacles.
Remember that when you build your SWOT analysis, point out everything in the corresponding boxes. Avoid abstract concepts and capture the information clearly enough to allow you to subsequently develop strategies to deal with it and achieve the objectives that are set.
These 4 drivers are: strengths, weaknesses, opportunities and threats.
With this analysis, it will be possible to identify the internal and external aspects that have the most impact, so that there is a clear vision that allows the development of future strategies to mitigate the risks and strengthen the positive aspects.
The SWOT analysis must be implemented at the beginning of a strategic planning process to have the most relevant and important aspects that indicate an approach to strategies to be applied. In a second phase, it is important to validate whether the factors indicated have changed in order to measure the effectiveness of the actions applied.
👉What should I take into account to carry out a SWOT analysis?
📌The template to be used to indicate the content for each of the forces is contemplated by a table divided into 4 boxes as follows:
📎Strengths
📎Opportunities
📎Weaknesses
📎Threats
📌Strengths
Place the internal factors of the organization, the product, the service, the brand or any other element to be analyzed. Here we answer question “what we do well?”.
📌Weaknesses.
In this box, point out the limitations of the existing processes, it can vary from the reduction of monetary funds to capacity deficiencies.
📌Opportunities.
Part, where we must identify areas where we have not ventured, alliances that have not been made but that have enough potential to become strengths.
📌Threats
Factors that cannot be directly controlled by you or your organization and that present themselves as obstacles.
Remember that when you build your SWOT analysis, point out everything in the corresponding boxes. Avoid abstract concepts and capture the information clearly enough to allow you to subsequently develop strategies to deal with it and achieve the objectives that are set.
❤3🔥1
Nice article about Product Backlog Refinement
https://www.scrum.org/resources/blog/product-backlog-refinement-how-succeed-scrum-team
https://www.scrum.org/resources/blog/product-backlog-refinement-how-succeed-scrum-team
Scrum.org
Product Backlog Refinement: How to Succeed as a Scrum Team
Garbage in, garbage out: Learn about 14 first principles to help your team succeed with an actionable Product Backlog.
🔥3
Hi! Let's do a small research.
What types of posts do you want to see here?
Feel free to suggest your own in the comments)
What types of posts do you want to see here?
Feel free to suggest your own in the comments)
Anonymous Poll
74%
Articles BA
36%
Articles SA
36%
Humor
40%
Recommended articles
21%
News
1%
Other
Today we will start fascinating topic "Top 5 Product Discovery Principles"🤓
So Discovery phase is inevitable in every project in case it really aims for success.
It is the very starting point of a product, and almost all roads are opened, but be careful: results of the discovery phase are going to have a dramatic effect during the whole product life-cycle and may determine its success or complete failure.
So it is very important to conduct the discovery phase properly.
The biggest possible mistake is trying to sit and write down the full product denoscription all by yourself without attracting appropriate specialists and conversing with potential customers and users.
No matter how genius you are, no one can do it alone.
Product Discovery Principles to Follow
⭐️Use standardized approach
Discovery is a phase with maximum uncertainty and it is a perfect place and time for creativity. That is why it is very important to not forget about something critically important. So we strongly recommend having a plan and using document templates, which will help you to ensure that you have not forgotten about something important.
⭐️Don’t dive too deep into details
The Discovery phase should not last long.
It should not be longer than 6 weeks even for huge projects. Diving into details is like swimming in a swimming pool with crocodiles - they are going to drag you into the depths and you will surely miss a lot of important things!
So during the Discovery phase, the product team should concentrate only on vision and scope. It is true both for business and technology issues. Diving too deep into details is counterproductive as it takes too much time and decisions made are still going to be reconsidered a lot of times in later stages of the product life cycle.
⭐️No is way more important than Yes
Starting a new Product is so inspiring! Such a huge bunch of ideas! There is always a big temptation to build a perfect product that should cure all diseases and make users' lives easier than ever. It is easy to lose your concentration and answer Yes to every idea that comes to your mind. At the end of the day, saying Yes is so much easier than saying No.
It is easy to lose connection with cruel market reality or design a Frankenstein which will be too complicated to use. So it is very important to be able to say No to even your favorite ideas! The truth is that only 1 of every 10 ideas is going to work.
The good thing is that you will be able to return to them later when the product is already in production and brings you profit.
Tomorrow we will continue this topic💛
#Discovery
So Discovery phase is inevitable in every project in case it really aims for success.
It is the very starting point of a product, and almost all roads are opened, but be careful: results of the discovery phase are going to have a dramatic effect during the whole product life-cycle and may determine its success or complete failure.
So it is very important to conduct the discovery phase properly.
The biggest possible mistake is trying to sit and write down the full product denoscription all by yourself without attracting appropriate specialists and conversing with potential customers and users.
No matter how genius you are, no one can do it alone.
Product Discovery Principles to Follow
⭐️Use standardized approach
Discovery is a phase with maximum uncertainty and it is a perfect place and time for creativity. That is why it is very important to not forget about something critically important. So we strongly recommend having a plan and using document templates, which will help you to ensure that you have not forgotten about something important.
⭐️Don’t dive too deep into details
The Discovery phase should not last long.
It should not be longer than 6 weeks even for huge projects. Diving into details is like swimming in a swimming pool with crocodiles - they are going to drag you into the depths and you will surely miss a lot of important things!
So during the Discovery phase, the product team should concentrate only on vision and scope. It is true both for business and technology issues. Diving too deep into details is counterproductive as it takes too much time and decisions made are still going to be reconsidered a lot of times in later stages of the product life cycle.
⭐️No is way more important than Yes
Starting a new Product is so inspiring! Such a huge bunch of ideas! There is always a big temptation to build a perfect product that should cure all diseases and make users' lives easier than ever. It is easy to lose your concentration and answer Yes to every idea that comes to your mind. At the end of the day, saying Yes is so much easier than saying No.
It is easy to lose connection with cruel market reality or design a Frankenstein which will be too complicated to use. So it is very important to be able to say No to even your favorite ideas! The truth is that only 1 of every 10 ideas is going to work.
The good thing is that you will be able to return to them later when the product is already in production and brings you profit.
Tomorrow we will continue this topic💛
#Discovery
🔥13
Today we will continue fascinating topic "Top 5 Product Discovery Principles"🤓
The next Product Discovery Principles to Follow
⭐️Prototype everything
Users don’t know everything. iPhone could never happen case Apple would only ask potential customers about what they wanted. If everyone could imagine your idea, it won’t be unique and potentially successful! Remember that users can only say yes or no to products that they can see and feel.
So every Idea should be prototyped and tested on real users - this is the only way to find out if it is going to work.
But don’t waste too much time on these prototypes! A napkin sketch is going to be just enough for the beginning - most of them are going to be reworked in any case. And after a napkin sketch is tested and approved, it is a good idea to ask a designer to prepare a clickable high-quality prototype without even writing a line of code.
And don’t forget testing!
⭐️ Concentrate on MVP
It is impossible to create a perfect product in just one go. So during the discovery phase, a project team should concentrate on one or two most critical users' problems and think about which way it can be solved in the easiest and fastest way to create an MVP and shorten the product’s way to market.
There is no need to cover everything, and by the way, it is almost impossible to do it appropriately.
Do you want to add some other principles❓
#Discovery
The next Product Discovery Principles to Follow
⭐️Prototype everything
Users don’t know everything. iPhone could never happen case Apple would only ask potential customers about what they wanted. If everyone could imagine your idea, it won’t be unique and potentially successful! Remember that users can only say yes or no to products that they can see and feel.
So every Idea should be prototyped and tested on real users - this is the only way to find out if it is going to work.
But don’t waste too much time on these prototypes! A napkin sketch is going to be just enough for the beginning - most of them are going to be reworked in any case. And after a napkin sketch is tested and approved, it is a good idea to ask a designer to prepare a clickable high-quality prototype without even writing a line of code.
And don’t forget testing!
⭐️ Concentrate on MVP
It is impossible to create a perfect product in just one go. So during the discovery phase, a project team should concentrate on one or two most critical users' problems and think about which way it can be solved in the easiest and fastest way to create an MVP and shorten the product’s way to market.
There is no need to cover everything, and by the way, it is almost impossible to do it appropriately.
Do you want to add some other principles❓
#Discovery
Our topic for today is "Product Discovery Tools"🛠
The modern world provides us with a lot of different tools to make the creative process more productive. Let me list just a few apps that we are using during the discovery phases:
📎Confluence for documentation.
📎Figma for interfaces design
📎Miro for ideating and product design
📎diagrams.net for schemas (aka draw.io)
📎InVision for creating live prototypes
But actually, it does not matter what tools you are going to use. Far more important is what artifacts you are going to create.
♦️Here are just the TOP 3 most important artifacts for almost any product discovery.
User personas
“User personas” is an instrument whose importance is really hard to overestimate.
It helps you to better understand your users, their needs, pains, experience with similar or competing products, and buying behavior.
This instrument also helps to understand who is going to become your main Users and prioritize the whole software development.
Customer journey map
Customer journey map shows Customer journey and their touching points with the product or service to achieve their goals.
It not only helps to better understand your customer and optimize their user experience, but also helps to understand who is going to be responsible for customer service at different stages of this journey, and in which way you can measure your success rates.
Fishbone diagrams and User story maps
Fishbone diagrams, Mind maps, and User story maps strongly help to elicit, visually organize and prioritize all features and underlying user requirements, to connect them with key Customer pains and form MVP scope.
#Discovery
The modern world provides us with a lot of different tools to make the creative process more productive. Let me list just a few apps that we are using during the discovery phases:
📎Confluence for documentation.
📎Figma for interfaces design
📎Miro for ideating and product design
📎diagrams.net for schemas (aka draw.io)
📎InVision for creating live prototypes
But actually, it does not matter what tools you are going to use. Far more important is what artifacts you are going to create.
♦️Here are just the TOP 3 most important artifacts for almost any product discovery.
User personas
“User personas” is an instrument whose importance is really hard to overestimate.
It helps you to better understand your users, their needs, pains, experience with similar or competing products, and buying behavior.
This instrument also helps to understand who is going to become your main Users and prioritize the whole software development.
Customer journey map
Customer journey map shows Customer journey and their touching points with the product or service to achieve their goals.
It not only helps to better understand your customer and optimize their user experience, but also helps to understand who is going to be responsible for customer service at different stages of this journey, and in which way you can measure your success rates.
Fishbone diagrams and User story maps
Fishbone diagrams, Mind maps, and User story maps strongly help to elicit, visually organize and prioritize all features and underlying user requirements, to connect them with key Customer pains and form MVP scope.
#Discovery
👍3
Let's talk about so important topic as GDPR🤓
👉The General Data Protection Regulation (GDPR) is the toughest privacy and security law in the world.
The purpose of GDPR is to provide clarity and consistency for the protection of personal information.
What you need to know about GDPR
📎 GDPR may be an EU mandate, but it also impacts every country
📎 GDPR requirements are applied to all kinds of personal data
📎 GDPR compliance requires to respects basic rights regarding personal data and data privacy
📎 You have to designate a representative in the EU
📎 There are hefty penalties for non-compliance with GDPR
📎 GDPR requires you to switch from an "opt-out" approach of data collection and data processing to an "opt-in" approach.
📎 GDPR compliance requires companies to clearly define their data privacy policies and make them easily accessible
📎 GDPR requirements set time limits for breach notifications
📎 GDPR requirements give data subjects the right to ask for their personal information
📎 According to GDPR requirements it may be necessary to hire a data protection officer
📎 Cloud-based storage is not free from following GDPR
📎 Human right are paramount, even at the expense of the user experience
What types of privacy data does the GDPR protect?
🔺Basic identity information such as name, address and ID numbers
🔺Web data such as location, IP address, cookie data and RFID tags
🔺Health and genetic data
🔺Biometric data
🔺Racial or ethnic data
🔺Political opinions
🔺Sexual orientation
In the next episode we will continue this topic.
Stay tuned⭐️
👉The General Data Protection Regulation (GDPR) is the toughest privacy and security law in the world.
The purpose of GDPR is to provide clarity and consistency for the protection of personal information.
What you need to know about GDPR
📎 GDPR may be an EU mandate, but it also impacts every country
📎 GDPR requirements are applied to all kinds of personal data
📎 GDPR compliance requires to respects basic rights regarding personal data and data privacy
📎 You have to designate a representative in the EU
📎 There are hefty penalties for non-compliance with GDPR
📎 GDPR requires you to switch from an "opt-out" approach of data collection and data processing to an "opt-in" approach.
📎 GDPR compliance requires companies to clearly define their data privacy policies and make them easily accessible
📎 GDPR requirements set time limits for breach notifications
📎 GDPR requirements give data subjects the right to ask for their personal information
📎 According to GDPR requirements it may be necessary to hire a data protection officer
📎 Cloud-based storage is not free from following GDPR
📎 Human right are paramount, even at the expense of the user experience
What types of privacy data does the GDPR protect?
🔺Basic identity information such as name, address and ID numbers
🔺Web data such as location, IP address, cookie data and RFID tags
🔺Health and genetic data
🔺Biometric data
🔺Racial or ethnic data
🔺Political opinions
🔺Sexual orientation
In the next episode we will continue this topic.
Stay tuned⭐️
❤11
Let's continue talks about as GDPR🤓
Which companies does the GDPR affect?
Any company that stores or processes personal information about EU citizens within and outside the EU. Specific criteria for companies required to comply are:
➖A presence in an EU country.
➖No presence in the EU, but it processes personal data of European residents.
➖More than 250 employees.
➖Fewer than 250 employees but its data-processing impacts the rights and freedoms of data subjects, is not occasional, or includes certain types of sensitive personal data.
Checklist
📌Be aware of the data you are collecting
📌Appoint a DPO (Data Protection Officer) to oversee the data protection strategy
📌Create a GDPR diary (Date Register) to record how an organization is practicing GDPR
📌Assess data collection requirements
📌Immediately report data breaches
📌Be clear about data collection motives
📌Verify the age of all users consenting to data processing
📌Include a double opt-in for all new email list sign-ups
📌Keep your Privacy Policy updated
📌Regularly assess all third-party risks
Which companies does the GDPR affect?
Any company that stores or processes personal information about EU citizens within and outside the EU. Specific criteria for companies required to comply are:
➖A presence in an EU country.
➖No presence in the EU, but it processes personal data of European residents.
➖More than 250 employees.
➖Fewer than 250 employees but its data-processing impacts the rights and freedoms of data subjects, is not occasional, or includes certain types of sensitive personal data.
Checklist
📌Be aware of the data you are collecting
📌Appoint a DPO (Data Protection Officer) to oversee the data protection strategy
📌Create a GDPR diary (Date Register) to record how an organization is practicing GDPR
📌Assess data collection requirements
📌Immediately report data breaches
📌Be clear about data collection motives
📌Verify the age of all users consenting to data processing
📌Include a double opt-in for all new email list sign-ups
📌Keep your Privacy Policy updated
📌Regularly assess all third-party risks
Are you a Business Analyst? Let’s talk about EBM, strategic planning, and glasses of beer as a measure of project success!
We’d like to invite you to Andersen's meetup in Krakow, where Senior Business Analysts and industry segment managers, who collected the best practices from their work in three comprehensive reports, will share their experiences with you. Along with valuable information, we guarantee subtle networking, pizza, and just a company of good people.
Are you in Krakow? Offline registration: https://lnkd.in/dRcfX_qz
Online registration: https://lnkd.in/dirDhbHp
And below is some more information about our speakers and their presentations!
1. Dzmitry Rusak (Business Analyst and Product Owner at Andersen)
Topic: Improve Product Value with EBM.
What is EBM (Evidence-Based Management)? EBM value within a project. EBM metrics. Feature prioritization based on EBM.
2. Paweł Sidorowicz (Team Lead and Business Analyst at Craftware)
Topic: "Do You Want to Grab Some Beer after Work?" as an Ultimate Measure of Success in Any Project.
You can use any framework, notation, or library, but if you don't build and sustain strong business relationships with stakeholders, you will never achieve success.
3. Filip Kopij (Business Analyst and Product Owner at Cytiva)
Topic: How to Harness Your Backlog Using Strategic Planning
How to prioritize a growing backlog? How to apply strategic planning to agile work? How to make sure you and your team follow the organization's strategic goals? I'll answer these and other questions during the session.
Seems useful, right? And it really is! Register using the link above and set a reminder in your calendar! See you!
We’d like to invite you to Andersen's meetup in Krakow, where Senior Business Analysts and industry segment managers, who collected the best practices from their work in three comprehensive reports, will share their experiences with you. Along with valuable information, we guarantee subtle networking, pizza, and just a company of good people.
Are you in Krakow? Offline registration: https://lnkd.in/dRcfX_qz
Online registration: https://lnkd.in/dirDhbHp
And below is some more information about our speakers and their presentations!
1. Dzmitry Rusak (Business Analyst and Product Owner at Andersen)
Topic: Improve Product Value with EBM.
What is EBM (Evidence-Based Management)? EBM value within a project. EBM metrics. Feature prioritization based on EBM.
2. Paweł Sidorowicz (Team Lead and Business Analyst at Craftware)
Topic: "Do You Want to Grab Some Beer after Work?" as an Ultimate Measure of Success in Any Project.
You can use any framework, notation, or library, but if you don't build and sustain strong business relationships with stakeholders, you will never achieve success.
3. Filip Kopij (Business Analyst and Product Owner at Cytiva)
Topic: How to Harness Your Backlog Using Strategic Planning
How to prioritize a growing backlog? How to apply strategic planning to agile work? How to make sure you and your team follow the organization's strategic goals? I'll answer these and other questions during the session.
Seems useful, right? And it really is! Register using the link above and set a reminder in your calendar! See you!
👍3
Let’s imagine that you have come up with an excellent business idea for a brand new product. You realize that the idea is more like your own hypothesis than a proven fact. That’s why you start asking yourself crucial questions shaping the future of a successful product: “Is there a real market need for the product?” “Who is the target audience?” “What are the key functionalities?” In addition, you want to have the ability to improve the product iteration by iteration. Here comes the concept of a minimum viable product, or MVP, which is of great help to business owners.
What the benefits of MVP development are?
MVP is a version of a product that has just enough features so that it can be tested by the first customers who provide feedback for future changes. What exact benefits does MVP offer a business?
📎Finding a market fit
MVP gives a company an opportunity to check in real life if there is any good demand for their future product. There is no sense in putting tons of effort into creating something that presents no interest at all.
📎Defining essential functionality
Every product sovles some problem that users have. Hence, your project goals and the needs of its target audience define what key features it must include to bring the most value to your business.
📎Raising investment
MVP software development doesn’t take long, however, the product perfectly reflects your project goals, contains main product features, and can be used to collect user feedback. Thus, startup leaders use them to present their ideas to investors and get the funding for their projects.
📎Optimizing resources
When you build an MVP, you focus all efforts on the features that users really need, and can calculate in detail their cost and time to develop. Therefore, it’s stongly recommended to go for an MVP to minimize product expenses and time to market.
In the next episode we will continue this topic.
Stay tuned⭐️
What the benefits of MVP development are?
MVP is a version of a product that has just enough features so that it can be tested by the first customers who provide feedback for future changes. What exact benefits does MVP offer a business?
📎Finding a market fit
MVP gives a company an opportunity to check in real life if there is any good demand for their future product. There is no sense in putting tons of effort into creating something that presents no interest at all.
📎Defining essential functionality
Every product sovles some problem that users have. Hence, your project goals and the needs of its target audience define what key features it must include to bring the most value to your business.
📎Raising investment
MVP software development doesn’t take long, however, the product perfectly reflects your project goals, contains main product features, and can be used to collect user feedback. Thus, startup leaders use them to present their ideas to investors and get the funding for their projects.
📎Optimizing resources
When you build an MVP, you focus all efforts on the features that users really need, and can calculate in detail their cost and time to develop. Therefore, it’s stongly recommended to go for an MVP to minimize product expenses and time to market.
In the next episode we will continue this topic.
Stay tuned⭐️
👍5