UX | 10 Examples of Good User Experience (UX)

10 Examples of Good User Experience (UX)
trone | Undated (Summer 2021 or before)

Websites & Apps that Understand Humans

  1. Rover: Using Reviews to Build Trust | https://www.rover.com
  2. Duolingo: Tearing Down Roadblocks | https://www.duolingo.com
  3. Paypal: Letting Simplicity Rule | (Mobile App)
  4. MailChimp: Humanizing Technology | https://mailchimp.com (Note: Intuit acquired MailChimp in Q4/2021, the current interface does not reflect the article, which predates the acquisition).
  5. Starbucks: Making it Personal | (Mobile App)
  6. Google: Loading Super Fast Since 1997 | https://www.google.com/
  7. Simple: Adding Clarity and Digestibility to Finance | (Mobile App)
  8. Nest Thermostat: Invisible Design | (Physical Product & Mobile App)
  9. Habitica: Using Gamification for Productivity | https://habitica.com/static/home
  10. Yelp: Everything Findable | https://www.yelp.com
  11. Bonus Example: From the Internet Archive (Poncho)

Author = Laura Flugga (trone)

URL = https://www.trone.com/blog/10-examples-good-user-experience-ux

Websites | Web Development Life Cycle

A Comprehensive Guide To The 7 Phases of Web Development Life Cycle
Monocubed | Jan 6, 2022 (Update), Nov 22, 2021 (Orig)

What is Web Development?
Software development life cycle or SDLC for website development includes-
the coding of the application logic
incorporating databases and managing user queries
designing user interfaces,
hosting the website on servers
maintaining and updating

Layers of Web Development
Server Side =
Backend or server-side development incorporates all the processes that go behind the scene in a website. The management of databases, servers, and logical components are the main components of the backend.
These are not tangible for the users, but without a strong backend development team, your website will be an empty page that can not do any tasks.
Client-Side = This layer, also referred to as the frontend, mainly deals with the visual presentation and designing of the site. Frontend developers work on creating a seamless user experience through responsive web pages using CSS, HTML, and JavaScript. Without a good user interface, your website will not be able to attract customers.
Full Stack = Full-Stack development combines the frontend and backend, encapsulating the whole web development process. In this layer, you deal with the entire stack of tasks and technologies involved in the website development cycle.
This means a full-stack engineer is adept at UI-UX designing, database manipulation, server hosting, and coding the browsers.

These three layers together encompass the web development life cycle. It remains the same for both website and web application development.

What is a Web Development Life Cycle? A web development life cycle concerns all the stages that go into building the website, from formulating the idea to coding and designing to deploying and maintaining. It is the standard or methodical step to follow to achieve a well-functioning website.

The 7 stages of web development cycle are –
Content creation

The 7 Phases of Web Development Life Cycle
Research and Analysis
Planning and Strategy
Designing and Wireframing
Content Creation
Code and Development
Front-end Web Development
Back-end Web Development
Testing and Quality Assurance
Deployment and Maintenance

Author = Jeel Patel

URL = https://www.monocubed.com/blog/web-development-life-cycle/

Roles | The Product Owner

HA #38: AMA session with Roman Pichler: The Product Owner | 58 minutes
Age Of Product | Feb 08, 2022

Stefan Wolpers’ Hands-on Agile #38: AMA w/ Roman Pichler: The Product Owner | 58 minutes

Stefan Wolpers’ AMA session with Roman Pichler on the role of the Product Owner.
Speaker: Roman Pichler | Host: Stefan Wolpers

My Notes:

Product Owner = Accountable for maximizing the value of the product
(Scrum Guide 2020)

What is a Product? An asset that creates value for
The users and customers
The company developing & providing it
(Searching for a product online = feature, not product)

What does it mean to own a product? It means
Being empowered to make strategic and tactical product decisions (own a product holistically, cf. Full Stack ownership)
Being responsible for achieving product success

Ownership Depth
Vision = what we want to achieve
Strategy = approach to get there
Tactics = information in the product backlog
Scrum Product Owner = Full stack ownership Vision/Strategy/Tactics
Product Manager in an Agile Context or Agile Product Manager
Compare w/ Partial Ownership
(SAFe = example) Product Owner = more a tactical role => product backlog, more inward facing, close to the Dev Team => Only partial ownership
(SAFe = example) Product Manager = for the Vision & strategic role

3 Scaling options
How to make it work? Get together and discuss it

About the Business Analyst

Characteristics of a great Product Owner
Professional PO (=> focus on the role of PO)
Committed to the Product, to the People, to the Process

About the Right Leadership

Backlog Management
Product Goal => only items that serve the product goal
Not too big, not too fast
Tie product backlog to product roadmap
Sometimes easier to start from scratch than try to make sense of a too large backlog (like thousand+ items)

Big products => Cascading goals
Mission statement
Challenge = Formulate the right goals & connect them in a meaningful way

Authors = Roman Pichler & Stefan Wolpers

URL = https://www.youtube.com/watch?v=LbXzaHaorTc

Planning | Product Roadmap

What is a Product Roadmap? And How to Create One
Product Manager HQ | Dec 22, 2021

The purpose of a product roadmap is to identify key steps to take and when to take them.
Crafting a product roadmap is no different from planning a road trip. Think about the last trip you planned. You likely first began by identifying key destinations, key dates, and a theme of what kinds of experiences you wanted to get from your road trip.

What is a Product Roadmap?
A product roadmap is a guide that describes the steps you need to take in order to reach your product goals. It’s a plan of action that lines up a product’s short-term and long-term goals. It also outlines how you hope to achieve those product goals.
Product roadmaps can span a variety of timeframes. That’s because different companies and teams can have different timelines.

Types of Product Roadmaps

  1. The Evolutionary Roadmap = This roadmap is a great tool for keeping everyone in sync when there isn’t a lot of information about how the final product will look. This type of roadmap is a solid choice to keep developers, designers, and project managers in sync.
  2. The Release Roadmap = This is the product or marketing team’s most important tool to communicate with the customer community about what features are going to be released and when. Product managers create release roadmaps once the product team has accomplished significant work on all major features planned for the release.
  3. The Theme Roadmap = This roadmap is a logical way to communicate the next features that will be implemented in an effort to meet company goals or customer needs. This map indicates where the product is going and how it plans to get there.
  4. The Timeboxed Roadmap = This is similar to the release roadmap but has more specifics about certain features or types of releases. Similar to a release roadmap, this map is detailed. However, it does not include dates. It serves as a reminder and communication for the team that work should be completed in time for a certain date.
  5. The Capacity Roadmap = This one is similar to the release roadmap but without dates. Capacity roadmaps serve as communication tools among departments or functions and show the types of products that the team will create. Product managers tend to use this product roadmap to discuss resources needed as opposed to specific deliverables.
  6. The Market Requirements Roadmap = This roadmap helps a company steer its product and market positioning. It also shows how the plan and types of products match requirements from the customer or user base.
  7. The Opportunity Roadmap = This one is used for companies that sell to businesses. It helps align business development efforts with strategic initiatives so that customers can be acquired in a coordinated way. For example, product managers create this type of roadmap once a significant amount of work has been completed on all major features planned for the release.
  8. The Project Roadmap = Product leaders use this roadmap to align teams and individuals working on different products or projects with each other. It lets people see how their work fits in with the rest of the company’s plans for that release.

How to Build a Product Roadmap
The first step in building a product roadmap is defining the product strategy. That comes from the vision you have for the product. Then, you and your team will need to gather information from two main sources. Those are your customer support or sales team and your product users.
This will give you a good base for assigning a timeframe to your initiatives.
Keep in mind that a product roadmap should be a strong foundation for all decisions, but it should be flexible. After all, the landscape might change and you might need to re-prioritize.

Why is a Product Roadmap Important?
A powerful product roadmap is built to serve a product strategy.
In product management, you’re faced with multiple viable alternatives all of the time. A product strategy mandates that you select one viable alternative out of many and that you say ‘no’ to many other alternatives.
Because a roadmap forces you to take your journey one step at a time, it means that you will take a specific step in a specific sequence. This helps the team to have a structured plan to follow.

Product Roadmaps Serve a Larger Purpose
They’re also powerful tools for aligning internal stakeholders with the direction that your product is headed. As an example, providing sales teams with visibility on where your product is headed will enable them to sell more confidently in the field. Doing so allows you to secure the buy-in of executives from various internal departments.

Product Roadmap Template
One simple way to structure your product roadmap is to ensure that each row includes the following columns:
New product feature idea
User story and requirements
Effort required = You’ll have to work with your team to figure out the best way to define the effort required. This could be a time or $ cost
Sequence = Which items should be done first? Which items should be done later? Be sure to use prioritization to identify what will give you the strongest ROI, or return on investment.
Estimated release date = Remember to keep this high-level and either come up with or work with your engineering manager to estimate the time required to complete the feature

Best Product Roadmap Tools
While product managers tend to be tool-agnostic, you can get ahead of the curve by familiarizing yourself with these popular roadmapping tools.
ProdPad: Lets you capture ideas and feedback, create product specs, and build a product roadmap.
ProductPlan: Lets you plan and communicate your product roadmap.
ProductBoard: System of record for product management that helps teams make products people want.
Aha!: Web-based product strategy and roadmapping software for agile product managers.
Roadmunk: Visual roadmap software for product management.
Jira: A flexible and scalable issue tracker for software teams.
Excel: A straightforward way to put together your thoughts.
Google Sheets: Easy for startups to use to quickly collaborate on feature ideas.

Author = Clement Kao

URL = https://productmanagerhq.com/what-is-a-product-roadmap/

Roles | Project Manager vs Scrum Master vs Product Owner

Project Manager vs Scrum Master vs Project Owner
Visual Paradigm | Undated

Role of Project Manager
The traditional Project Manager is a leader, a decision maker, a planner who manages the project and his team and is the person accountable to the business for accomplishing the project objectives. Project manager’s role is to manage the projects and ensure that the project meets the requirements.

The roles and responsibilities of the Project Manager includes:
Define project scope
Gather requirements
Identify activities, dependencies, sequencing, and time estimates.
Identify resources needed
Manages the budget
Reports to business leadership on project progress
Focuses on process
Allocates tasks
Prioritizes features
Ensure quality
Manage vendors
Manages risk

Role of Scrum Master
The Scrum Master doesn’t manage the team that produces the work, instead he supports the Product Owner, coaches the team and makes sure that Scrum processes are adhered to. The Scrum Master is responsible for the Scrum process, its correct implementation, and the maximization of its benefits.

The role of the Scrum Master is more a coaching and facilitation role, a role that sits between the project and the customer and the role includes:
Lead Sprint Planning
Lead / Organize the daily Scrum Meeting
Coaches the product owner
Monitoring the progress of the sprint
Helps team estimate and increase velocity
Promotes continuous communication
Reduce team disruptions
Monitors and helps improve team dynamics
Assist with Reporting
Motivates the team
Acts as the glue that holds the team together

Role of Product Owner
Product Owners have a huge responsibility for the project. They are responsible for maintaining a product backlog that describes the product that must continue to fit with the requirements of the business. During any project, as more becomes known about a product, about customers, or about changes in the market, a product often needs to change in order to meet these requirements. The Product Owner has to adjust and re-prioritise the backlog to fit these changes and to steer the project.

Project Owner’s role includes:
Convey a clear vision of the project
Manage and prioritize product backlog
Ensure development team understand tasks and work on the right features in the prioritized order
Provide feedback and sign off work results

Difference between Project Manager and Scrum Master
In Waterfall, the Project Manager takes a leadership role in leading the team and developing and managing the plan. But what about all those project management activities if the team is Agile?
A project manager helps manage the project timeline, resources, and scope in order to meet business requirements. A Scrum Master, however, helps ensure the scrum team is successful.
A Product Owner works with the customer and team to set direction.
A Scrum Master is a coach and facilitator and coaches the development team in executing Agile practices to complete the work the Product Owner prioritizes.
The Scrum Master works with the Product Owner and the development team to ensure the team members can move forward with development with no impediments, and that the Scrum practices are carried out.

Note That: There is a time or place for a project manager in the large projects. The Project manager can cover multiple teams and can work with other dependent teams as well. Project manager can coordinate with multiple teams, help them to meet project timelines and collaborate when resources are required.

URL = https://www.visual-paradigm.com/scrum/project-manager-vs-scrum-master-vs-project-owner/

Mobile Apps | Case Studies (Peerbits)

peerbits App Case Studies
peerbits | Undated

Real-time tracking app, real-time tracking and remote diagnostics
URL = https://www.peerbits.com/case-studies/real-time-tracking-solution.html

Social networking iOS app, connect with new people
URL = https://www.peerbits.com/case-studies/social-networking-app-for-iphone.html

Petrol filling station app, the official app for the largest chain of filling stations in Oman
URL = https://www.peerbits.com/case-studies/petrol-filling-station-management-app.html

ATM food solution, an IoT-controlled automated marketplace
URL = https://www.peerbits.com/case-studies/atm-food-solution.html

Marketplace app, GetItDone
URL = https://www.peerbits.com/case-studies/getitdone.html

URL = https://www.peerbits.com/case-studies/m2r.html

Fishency, building a better way to fish like a pro
URL = https://www.peerbits.com/case-studies/fishency.html

URL = https://www.peerbits.com/case-studies/jewlot.html

Nurse Alert, a cohesive solution to nursing activity
URL = ttps://www.peerbits.com/case-studies/nurse-alert.html

Apply, a tinder-like job search app
URL = https://www.peerbits.com/case-studies/apply.html

Photograff, Graffiti
URL = https://www.peerbits.com/case-studies/photograff.html

URL = https://www.peerbits.com/case-studies/repd.html

Epic Delivery
URL= https://www.peerbits.com/case-studies/epic-delivery.html

Throne, the eCommerce Marketplace App
URL = https://www.peerbits.com/case-studies/throne.html

URL = https://www.peerbits.com/case-studies/seatsplanet-travel-app.html

BusMaps, plan bus trip with navigation travel app
URL = https://www.peerbits.com/case-studies/busmaps-navigation-app.html

URL = https://www.peerbits.com/case-studies/tapnsell.html

Loyal Books

Frimb, Food & Drink app that connects socially and share recipes globally with food lovers
URL = https://www.peerbits.com/case-studies/frimb-food-drink-app.html

Fashion Sizzle, capture and share the clothing trends with fashion lovers on FashionSizzle. success story
URL = https://www.peerbits.com/case-studies/fashion-sizzle-photo-app.html

Peerbits Works
URL = https://www.peerbits.com/works.html

Author = peerbits

URL = https://www.peerbits.com/case-studies.html

Mobile Apps | Terms & Conditions

Mobile App Terms and Conditions Template
Termly Legal Team | Nov 13, 2020

Table of Contents
What Are Mobile App Terms and Conditions?
Are Terms and Conditions for My Mobile App Required?
App Store Terms and Conditions Requirements
Common Clauses to Include in Your App Terms and Conditions
Terms and Conditions By App Type
Getting User Agreement to Your App Terms and Conditions
Mobile App Terms and Conditions Samples
How to Write Terms and Conditions for Mobile Apps
Free Mobile App Terms and Conditions Template
App Terms and Conditions FAQs

Author = Termly Legal Team

URL = https://termly.io/resources/templates/app-terms-and-conditions/

Agile | Agile VS Waterfall

Advantages of Agile Product Methodology for Fast Growing Startups & Enterprises
B2C Business2Community | 19 April 2021

What is Agile Product Methodology?
Agile product methodology is a practice which promotes continuous development and testing of a software or product throughout the product development lifecycle. In this approach, both the development and testing activities remain concurrent.
Agile approach is known to be one of the most effective and simplest processes to turn a vision for a product into software solutions.

Agile Development Statistics:
85.9% of software developers around the world use Agile product methodology
Companies that use Agile approach for software development gain 60% more profits than those who don’t.
Agile success rates are more than 1.5x higher than those of Waterfall projects
According to Agile adoption statistics, plenty of Fortune 500 companies have adopted Agile

Agile Product Methodology Vs Waterfall Model
Waterfall Approach

  1. In the Waterfall approach, product development flows sequentially from one point to another; just like a Waterfall filling the next reservoir.
  2. Using Waterfall development means customers will see the product only at the end of the project
    Waterfall method is considered to be more secure because it is plan oriented.
  3. In the Waterfall method, errors are tested only when the whole product is ready. So, if changes are to be made, the product development has to start from the beginning.
  4. In the Waterfall method, product developers and testers work separately.
  5. All features of a software or product are delivered at once, at the end of the project, and after the long implementation phase.
    Agile Approach
  6. Agile method follows incremental approach to product development.
  7. Agile method promotes early launch of products. Customers get early and frequent chances to use the product. This helps product development teams in making decisions and do necessary changes to the product.
  8. Agile method is comparatively unstructured as compared to the Waterfall method.
  9. Agile allows product development teams to fix errors in the middle of the project. Within this method, teams continue to test products throughout the product life cycle and gain useful feedback from the customer.
    In the Agile method, both testers and product developers work together.
  10. In Agile product development mode, core features of a product are delivered to users, and new features are added over time.

Agile Methodology Advantages
Put simply, Agile is:
Iterative – involves regular rhythms of work
Incremental – requires product development teams to present product increment
Faster: It ensures faster reach to the market
Cost-Efficient: Agile reduces cost of development by allowing product development at the same time teams gather requirements and information
Responsive: product teams can respond immediately if there’s an unpredictable scenario and revamp the product accordingly.

How to Use Agile Methodology in Product Development
Agile teams follow these steps to create products:

  1. Project Initiation
  2. Create Backlogs
  3. Establish Sprints for Software Development
  4. Product Development
  5. Production and Deployment

Agile Product Development Processes (Framework)

  1. Scrum
  2. Kanban
  3. Extreme Programming (XP)

Case Study of Agile Methodology

Author = Chanakya Kyatham

URL = https://www.business2community.com/startups/advantages-of-agile-product-methodology-for-fast-growing-startups-enterprises-02394643

UX | UX Storyboard Creation: Complete Guide

UX Storyboard Creation: A Complete Guide For Beginners
uxstudio | Mar 12, 2019

UX storyboard creation seems like a slightly overlooked design technique. We all know the value of user interviews or personas. We agree that testing is a crucial part of product design. In contrast, people do not commonly use storyboarding, even though it can help in many situations. As a true fan of the technique, in this guide, I want to walk you through all the whys and hows of UX storyboard creation. Plus, I even made a free template for you to get started!

What is a storyboard?

Storyboards in product design
We have personas and journeys. Why do we need UX storyboard?

  1. Visual benefits
  2. Emotional engagement
  3. Memorability
    When to storyboard?
  4. During the discovery phase of a new product
  5. While building the product
    Typical scenarios
  6. Mapping a whole service
  7. Digital product with offline events
    Important note: Drawing skills don’t matter!

How to design a first UX storyboard

  1. Step one – Get some data!
  2. Step two – Pick a flow to focus on
  3. Step three – Write down the plot steps and basic outline of the story
    The main character
    Plot Steps
    For some guidance at this stage, feel free to download our free Storyboard Template:
  4. Step four – Add emotions and scene details
  5. Step five – Create the storyboard!

Author = Luca Morovián (uxstudio)

URL = https://uxstudioteam.com/ux-blog/ux-storyboard/

Mobile Apps | Requirements

Functional and Non-Functional Requirements for Mobile App: What’s the Difference?
Lvivity Team | February 20, 2021

Functional requirements for mobile applications describe what specifically needs to be implemented in a particular system or product and what actions users have to take to interact with the software. They determine what the system should do.

Non-functional requirements for mobile app show what properties and features a particular solution has, namely, how the system will work and why.

What do Functional Requirements Include?
We can highlight three main groups of functional requirements:
Business requirements. These define the high-level goals set by the customer’s company that is ordering the software development and stipulate what the system is to solve in terms of their business. Example: an application allowing potential customers to browse through the company’s product catalog and to purchase products.
User requirements. These describe the system goals/objectives the users may reach when using the created system (UseCases). Simply put, this is what a user can do: sign up, view certain content, recalculate data using a specific algorithm, and other functions.
Functional requirements. These define a list of actions the system has to perform. In addition, they have to specify how the system responds to various input data, how it behaves in particular situations, and so on.
This group also includes system requirements describing hardware and software environment features necessary for correct operation.

Non-Functional Requirements in Simple Words

As a rule, the non-functional requirements primarily include various product quality attributes determining system quality features, most often as examples below:
Availability – requirements for app continuous running, for example, 24/7, minimum idle time, etc.
Reliability – app behavior in case of alarm status, for example, automatic restart and operation recovery.
Scalability – ways to expand the system and avoid adversely affected performance.
Performance – how many simultaneous users or transactions the system is to service and its response time.
Security – app operation and use of safety requirements related to access control, private data processing, and external attack risk reduction.
Usability – ease of use and user-friendly interface, that allow users to seamlessly interact with the product.
Extensibility – requirements for app extensibility in case there is a need to add new functional requirements.

Wikipedia = Non-functional requirement
URL = https://en.wikipedia.org/wiki/Non-functional_requirement


Author = Lvivity Team

URL = https://lvivity.com/functional-and-non-functional-requirements