Websites | Staging Site

What Is a Staging Site? How Do You Set One Up?
WPEngine (WordPress) | Jan 12, 2022

What is a staging site? To put it simply, a staging site is a clone of your live website. It enables you to test any changes or major new features that you plan to implement in a secure environment. Developers typically use staging sites to test changes and fix bugs before going to production.
Your staging site is intentionally identical to your live site—same plugins, same settings, same widgets, and so on. The only real difference between your live website and a staging site is that the latter is not live.
Instead, it exists in a sort of sandbox where you can see how your website would react in everyday scenarios. Anything that happens in the staging environment won’t affect your live website.

Development vs. QA vs. Staging vs. Production Sites
Most common types of WordPress testing environments that are used during development:
Development website. This environment contains all the latest iterations of the code you’re working on. It’s perfect for initial testing of new features.
Quality Assessment (QA). During the QA process, changes to your website will be tested thoroughly to find any issues that you may have missed while coding. This type of environment is most often used by large companies, since they can’t afford to have bugs pop up on live sites.
Staging website. A staging website acts as the bridge between the development and live versions of your site. At this point, any remaining errors should be addressed, and the changes should be ready to roll out.
Production website. This is the live version of your website that users will see. If you’ve been careful throughout the development process, this iteration of your WordPress site should be bug-free and provide a flawless user experience.

Staging Environment vs. Testing Environment

The Benefits of Using a Staging Site
Enable you to produce better websites
Provide you with the opportunity to catch errors and bugs without putting your site at risk
Are usually simple to create
Can be set up locally or online (depending on your preferences)

The Drawbacks of a Staging Site
It takes longer to update your website (as you need to test changes first).
Web hosts often charge for a staging site service (although you can always set one up locally).
Staging sites may not be exact replicas of a live website (caching is not usually enabled on a staging site, for example).

Who Needs a Staging Site? Ideally, everyone who runs a website needs a staging test site. However, if we’re being practical, staging websites should be used at the very least by anyone who runs a sizable operation.

How to Create a Staging Site for WordPress
Option 1:
Set Up a Staging Test Site Through Your WordPress Host
Option 2: Using a WordPress Staging Plugin to Create Your Staging Sandbox
Option 3: Set Up a Local Installation

Should You Create a Staging Site Manually?
How to Deploy Changes to Your Live Site
Develop Safely With WP Engine

Author = Erin Myers

URL = https://wpengine.com/resources/what-is-a-staging-site-why-have-one/

User Stories | 10 Tips For Writing Good User Stories

10 Tips For Writing Good User Stories
Roman Pichler | Mar 07, 2022 (Update)

1 Users Come First
2 Use Personas to Discover the Right Stories
3 Create Stories Collaboratively
4 Keep your Stories Simple and Concise
As <persona>,
I want <what?>
so that <why?>.

5 Start with Epics
6 Refine the Stories until They are Ready
7 Add Acceptance Criteria
8 Use (Paper) Cards
9 Keep your Stories Visible and Accessible
10 Don’t Solely Rely on User Stories

Author = Roman Pichler

URL = https://www.romanpichler.com/blog/10-tips-writing-good-user-stories/

Tools | 13 product management tools the best Product Managers use

13 product management tools the best Product Managers use
Medium | Apr 01, 2022

Always good to get a refresher on what is being used by others. Which tools do you use?

Phase 1: Opportunity identification and validation
(1) Google Sheets (Spreadsheets) https://www.google.com/sheets/about/
(2) Notion (Taking Notes) https://www.notion.so/
(3) Field (Collect, Explore, Present) https://field.so/en

Phase 2: Design and prototyping
(4) Miro (Collaborative Whiteboard) https://miro.com/
(5) Figma (Collaborative Design & Prototyping) https://www.figma.com/
(6) Pen & Paper
(7) Pitch (Collaborative Presentations) https://pitch.com/

Phase 3: Feature development
(8) Confluence (Team Workspace) https://www.atlassian.com/software/confluence
(9) Jira integration (Agile Software Development) https://www.atlassian.com/software/jira
(10) Google Docs (Drafting Documents) https://www.google.com/docs/about/
(11) Trello (Productivity) https://trello.com/

Phase 4: Launch and continuous iteration
(12) UXCam (Analytics – Note: plug) https://uxcam.com/
(13) Grammarly https://www.grammarly.com/

Author = Jane Leung, UXCam

https://medium.com/@uxcam_/13-product-management-tools-the-best-product-managers-use-95ca6006a00e

Websites | Average Time Spent On A Website

What Is the Average Time Spent On a Website? [+ How to Improve It]
HubSpot | Dec 22, 2021 (Update) Mar 2014 (Orig)

Average Time Spent on a Website
Average time spent on a website, like average time on page, is dependent on a range of factors. Industry, the type of website, and even the device that users are on impact this average.
For example, Statista calculated the 20 most popular websites worldwide as of June 2021, by time per visit. Users spent approximately 22 minutes and 44 seconds per visit on Google, the most popular website, and only .54 minutes on VK.com, the 20th most popular.

How to Improve Average Time Spent on a Website
Decrease load time.
Optimize your navigation.
Add internal links.
Improve the readability of your posts.
Add images and videos.
Optimize for all devices.
Use exit intent popups.

Author = Anna Fitzgerald

URL = https://blog.hubspot.com/marketing/chartbeat-website-engagement-data-nj

Metrics | Product Management — All about Metrics

Product Management — All about Metrics
Medium | Mar 02, 2022

Comparison between Facebook & Twitter and their use of Engagement & Growth Metrics

What makes a good metric?
(1) Strategic
(2) Understandable/Actionable/Relevant/Referenceable
(3) Rate or Ratio
(4) Correlation vs. Causation
(5) Changeable

Metric rollup
Counter metric
Exploratory vs Reporting Metrics

Methods to select your perfect metric
HEART = Happiness, Engagement, Adoption, Retention, Task (Kerry Rodden)
Across these dimensions, you will identify goals, signals, and metrics to measure how well your product is doing.
Goal = something the user is trying to do or something you are trying to help them to do
Signal = a change in user behavior that indicates that the user is achieving the goal
Metric = a way to measure signal and quantify how much user behavior has changed

Concludes with a walk you through an example for an imaginary product.

Author = Alaa MohyEldin

https://alaamohy.medium.com/product-management-all-about-metrics-30ec93259e9a

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 –
Research
Planning
Designing
Content creation
Development
Testing
Maintenance

The 7 Phases of Web Development Life Cycle
Research and Analysis
Purpose
Requirements
Expectations
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

Abstract
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
Available/full-time
Professional PO (=> focus on the role of PO)
Committed to the Product, to the People, to the Process
Qualified

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)

Goals
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

Mobile Apps | Development Proposal Examples

Mobile Apps | 10+ Mobile App Development Proposal Examples in PDF
Examples.com | Undated

What Is a Mobile App Development Proposal?
A mobile app development proposal is a document that developers devise to promote their application. Through this proposal letter, they can request and negotiate a partnership or sponsorship. The purpose of this paper is to attract potential clients to purchase the mobile application. A business proposal is a complex document that involves a lot of necessary segments.

  1. Mobile App Development Strategies Proposal
  2. Mobile App Proposal Template
  3. Mobile App Pre-Development Proposal
  4. Mobile Application Developer Proposal
  5. Android Mobile App Development Proposal
  6. Mobile App Development Project Proposal
  7. Mobile App Development Form of Proposal
  8. Local Mobile App Request for Proposal
  9. Notice of Mobile App Request for Proposal
  10. Mobile App Development Partner Proposal
  11. Mobile App Financial Proposal

How to Construct an Impressive Mobile App Development Proposal

  1. Think Up a Gripping App Name
  2. Compose an Engrossing Cover Letter
  3. Structure Your Proposal
  4. Include a Cost Management Plan

FAQs
What are the things to do before starting to develop a mobile app?
What are the elements of a business proposal?
What should be in the cover letter of a project proposal?

Author = Examples.com

URL = https://www.examples.com/business/proposal/mobile-app-development-proposal.html