Archives: Documents

Introduction

1  Purpose of the Document

This guide explains the process for developers to get a new application integrated into the CI/CD pipeline and how to deploy it to various environments.

2 The Core Workflow:

Onboarding is a collaborative process:

• The Developer prepares the application and requests a new pipeline.
• The DevOps Team builds the necessary infrastructure: Dockerfile, Jenkinsfile, task-definition.json, AWS resources, and the Jenkins job itself.
• The Developer triggers all deployments manually through the Jenkins UI.

Step 1: Developer Preparation

This is what you need to do before requesting your pipeline.

1 Prepare Your Source Code:

• Ensure your application code is in a GitHub repository under the Memorres organization.

2 Define All Required Configuration:

• Create a definitive list of all environment variables and secrets your application needs to run.
• The DevOps team will use this list to create the infrastructure/task-definition-<environment_name>.json file for your service.

Step 3: How to Deploy Your Service

All deployments are initiated manually from the Jenkins UI. This gives you full control over when a new version is released.

1 How to trigger a deployment

1. Log in to the Jenkins server with your provided credentials.
2. Navigate to your service’s pipeline job. Your access is role-based, so you will only see the projects you are assigned to.
3. Select the branch you wish to deploy (e.g., main, develop, hotfix/urgent-fix).
4. Click “Build Now” to start the pipeline. The pipeline will build the code from the latest commit on that branch and deploy it to the corresponding environment.

Verification and Troubleshooting

The CI/CD process ensures that code changes are integrated, tested, and deployed consistently and reliably. The process is broken down into the following stages:

1 Verifying Deployment

• Check the application URL and review logs in CloudWatch to confirm a successful deployment.

2 Troubleshooting

• Application Errors (e.g., failed tests): Fix the code, push to your branch, and run the Jenkins job again.
• Pipeline Errors (e.g., Docker build fails): Contact the DevOps team in the #devops-support Slack channel with a link to the failed Jenkins build.

At Memorres, culture is not decoration on a wall — it is how we show up in every call, email, design, line of code, or client workshop.

The purpose of this document is to make sure every employee and manager knows what “great” looks like here, and why it is non-negotiable.

These standards exist to protect the reputation we have built, guide daily decisions, and keep us consistent as we scale. In real work, you will face pressures to move faster, deliver cheaper, or cut corners. This document draws the line: we never trade standards for shortcuts.

The scope of these standards covers every person in Memorres, regardless of title or department. Whether you are onboarding a new client, preparing a deliverable, leading a meeting, or supporting a colleague, the same bar applies. Standards are not only for leaders — they are a shared responsibility.

To make them usable, each standard is broken down into clear meaning, non-negotiables, and how leaders model it. These are not abstract values but visible actions. Alongside the standards, this document explains the rhythm by which we live them: onboarding sessions, monthly reflections, and quarterly reviews. Together, these create a system where standards are explained, practiced, and measured.

Definitions

Standards only work if everyone interprets them the same way. At Memorres, we avoid vague slogans. Instead, we define what our terms mean in practice so no one is left guessing.

The table below lays out the core definitions that will appear throughout this article. These definitions are not academic; they are practical tools that you can use in daily work, in reviews, and in coaching conversations.

These definitions are anchors for the rest of this article. When we talk about holding the bar, modeling behavior, or reviewing deliverables, you can come back to this table and see exactly what is meant.

Standards are only powerful if they are clear. With these definitions in place, every employee and manager can see the same picture of what we expect and how we measure it.

The Four Standards

Brand Standards – How We Show Up to the World

Every interaction we have with the outside world reflects on Memorres. A sloppy email, a broken link, or a rushed presentation doesn’t just look bad — it signals that we are careless in our work. Our brand is the first impression, and in many cases, it decides whether clients and partners trust us.

Brand standards are not about fancy designs or creativity contests. They are about discipline, consistency, and professionalism. A clear message, error-free communication, and a design that matches our identity show that we respect our work and the people we serve.

When you prepare any client-facing or public-facing material, ask yourself: “Does this show Memorres at its best?” If the answer is no, don’t send it. Fix it.

These standards protect us from the silent damage of small mistakes. A typo may look small, but it raises questions about whether we might also cut corners in our code, design, or delivery. By holding the line on brand, we send a message: Memorres takes pride in its work, down to the last detail.

Product (Service) Standards – The Quality Bar

At Memorres, our “product” is not a physical item. It is the work we deliver: a line of code, a design file, a workshop, a report, or a campaign. Clients don’t see our effort; they only see the output. That output is our reputation. If it is sloppy, incomplete, or rushed, the message is simple — Memorres cannot be trusted.

Product standards are about raising the quality bar so that no deliverable leaves the company half-ready. They remind us that ticking a box is not the same as solving a problem. If the work doesn’t address the client’s real need, it is not ready.

A rushed draft may save a few hours today but cost weeks of reputation tomorrow. That’s why leaders at Memorres return weak work without apology — it is not personal, it is about protecting the company’s name.

When in doubt, apply the Definition of Ready (DoR) before sending work out, and confirm the Definition of Done (DoD) before delivery. These checklists ensure no important step is skipped. They are not paperwork; they are shields against avoidable mistakes.

Product standards exist to remind us that clients hire Memorres not for “good enough,” but for excellence that stands up to pressure. Every deliverable is a chance to prove why they chose us.

Performance Standards – What Great Work Looks Like Here

At Memorres, excellence is expected from everyone. This doesn’t mean every person has to be a superstar, but it does mean everyone clears the bar of professional, reliable work. Performance standards make it clear what “good” looks like here, so there is no confusion about expectations.

Meeting deadlines or showing up to a meeting is not an achievement — it is the baseline. Real performance comes from owning your tasks, communicating clearly, and delivering work that others can depend on. When one person misses the bar, the whole team feels the effect.

Performance is not only about outcomes but also about how those outcomes are achieved. Clear communication, proactive updates, and ownership of mistakes are as important as technical skills.

To keep performance visible and fair, Memorres uses scorecards. These scorecards define three levels — acceptable, exceptional, and unacceptable — for key areas such as delivery reliability, communication, and collaboration. They are reviewed quarterly, so no one is left wondering where they stand.

The message is simple: great work here means reliable delivery, honest communication, and steady ownership. If you can be counted on, you will grow at Memorres. If you cannot, you will not fit here.

Leadership Standards – How We Show Up Every Day

Leadership at Memorres is not tied to a title. It is about how you act, whether you are a CEO, a project manager, a designer, or a developer. People watch and learn from how others behave, not just what they say. That is why leadership standards matter at every level — culture spreads through example.

True leadership shows up in how we communicate, how we handle conflict, and how we support others. It is about being prepared, staying consistent, and keeping respect at the center of every interaction. Passive-aggressive behavior, hidden conflicts, or neglecting people are never acceptable here.

In practice, this means raising concerns openly, giving feedback without delay, and aligning once decisions are made. It means coaching team members, not just managing deliverables.

Leadership standards also set the rhythm for growth. Every quarter, leaders hold conversations with their team members — not just about tasks, but about development, aspirations, and support needs. These talks build stronger people, and stronger people build stronger work.

At Memorres, leadership is not optional. It is the daily behavior that keeps the culture alive and makes scaling possible. When everyone leads by example, we create an environment where high standards feel natural, not forced.

Action Plan – How We Live the Standards

Standards are only valuable if they are lived every day. At Memorres, we don’t leave culture to chance. We train people on it, review it regularly, and hold ourselves accountable. The action plan below explains how these standards move from words to practice.

Training and Embedding

From the first day, every employee learns what these standards mean. New hires review them during onboarding, so there is no confusion about expectations. Teams also take part in one-time workshops where real examples are discussed — both good and bad — so the standards are not just theory.

To keep the bar visible, deliverable templates include a simple “Standards Check” step. Before anything goes out, the person responsible confirms it is brand-ready, meets the product/service bar, clears performance expectations, and is modeled in leadership behavior.

Monthly Cadence (Feedback & Review)

Quarterly Cadence (Accountability & Growth)

By following this rhythm, we make sure standards are explained, practiced, and measured. They stop being slogans and become habits that protect Memorres as we grow.

Annual Calendar

Standards need rhythm to stay alive. At Memorres, we use a simple annual calendar that combines monthly focus calls with quarterly reviews. This ensures we don’t just talk about standards once a year but revisit them consistently. Each month has a dedicated focus, and every quarter we pause to look at the bigger picture.

The calendar is not just for leadership — it involves every employee. Monthly calls bring learning and recognition, while quarterly reviews drive accountability and growth. By following this cycle, we keep standards fresh, visible, and actionable.

This structure gives balance:

• Monthly calls are short, reflective, and focused on a single area.
• Quarterly reviews look at all four standards and drive accountability with leaders and individuals.
• December wrap-up gives everyone a moment to reflect on the year, celebrate progress, and recommit for the next cycle.

The calendar makes sure standards are not a one-time push but a continuous loop. Employees know when feedback will come, managers know when accountability is due, and leaders know when to reaffirm commitment. This predictability builds trust and ensures the standards guide us throughout the year.

Closing Note

These standards are not optional. They are the playbook for how Memorres works and grows. They protect our reputation, guide our daily choices, and ensure that as we scale, we never lose the culture that makes us strong.

Every employee and manager is responsible for living these standards. They are not words to be skimmed once and forgotten — they are expectations to be practiced every day. From a quick email to a client presentation, from handling feedback to mentoring a teammate, the standards show up in small details and big moments alike.

The CEO is the guardian of these standards, but leadership is shared. Each of us models culture by how we act, speak, and deliver. If we compromise once, it becomes easier to compromise again. That’s how trust and quality erode. The opposite is also true — when we hold the bar consistently, people learn to trust Memorres more deeply over time.

By committing to these standards, we make sure Memorres is not just another service company but one known for trust, consistency, and quality.

Scaling a company always brings pressures: move faster, go cheaper, cut corners. At Memorres, we have chosen a different path. We will grow without losing our soul — because we know that culture is our greatest advantage.

Purpose

The purpose of this guide is to help QA teams at Memorres prepare reports that are not just technical summaries but clear, client-ready documents. While internal dashboards can capture granular details, client-facing reports must translate those details into language and structure that business stakeholders can understand. This guide explains how to prepare reports that are accurate, professional, and valuable in building client trust.

Scope

This guide applies to all QA Leads and Engineers preparing reports for clients across SaaS, web, and mobile projects. It covers weekly QA summaries, release readiness reports, and end-of-project QA extracts. It does not cover internal-only dashboards or retrospective reports used exclusively within the QA team.

Guidance

Client-facing QA reports at Memorres are structured around four principles: Clarity, Relevance, Transparency, and Professionalism.

Report Types

1. Weekly QA Summary
   • Purpose: Keep the client informed of progress.
   • Content: Coverage %, key defects, severity breakdown, blockers, next steps.
   • Format: 2–3 page PDF or Excel snapshot.
2. Release Readiness Report
   • Purpose: Confirm if the product is ready for release.
   • Content: Entry/exit criteria validation, critical defect status, risk matrix.
   • Format: Formal document signed by QA Lead.
3. End-of-Project QA Extract
   • Purpose: Share lessons learned, recurring issues, and improvement recommendations.
   • Content: Trends, systemic issues, defect patterns.
   • Format: Knowledge artifact stored in MIC.

Example – Executive Summary Extract

Closing Note & Cross-References

Client-facing QA reports are more than numbers; they are tools of communication and trust. By applying clarity, relevance, transparency, and professionalism, QA teams ensure that clients receive accurate insights into quality and delivery readiness.

This guide connects directly to the QA Metrics & Reporting Validation Checklist, which validates accuracy of data, and the QA Summary Report Template, which standardizes reporting format.