01 Sales - ISO 9001:2015 Process.

Mobomo works with potential customers during the sales process to ensure that our team fully understands requirements, goals, and pain points to guarantee that we craft a team and solution that maximizes impact and value.

• Identify opportunities where Mobomo can maximize value based on our core competencies in digital transformation (web, mobile, cloud, agile, human-centered design, DevSecOps) and strategic focus (new and emerging technologies and best practices including total experience, artificial intelligence, machine learning, blockchain, and hyper-automation).
• Work with the customer to truly understand business and technical needs, craft statement of objectives, develop requirements, and establish trust.
• Assemble a world-class team with experience, business understanding, and intimacy with the customer’s organization, environment, and mission.
• Do not pursue work where our team cannot succeed.
• Develop an innovative solution to meet in Agile, if not exceed, all customer requirements and expectations based on our proven CMMI / ISO, IMPACT ™ methodology.
• Provide the best value to the customer by competitively pricing the solution, maximizing automation and technical expertise.
• Ensure a seamless transition to execution through pre-kickoff briefings and the creation of the Confluence project site with all requirements, deliverables, and deadlines upon notification of award.

Once our sales process is complete--and depending on timelines, budget, and resources--we’ll then move on to the project kickoff.

02 Project Kickoff.

We kickoff our project with a meeting where we thoroughly review the business goals, requirements, and deliverables of the project with the client. Our kickoff meetings set the expectations, timelines, and overall management of the project. The client can ask questions, clarify processes, and define priorities for the project. We cover introductions, takeoff checklist, SOW tasks and deliverables, contact information, meeting plan, communication plan, roadmap, and task management.

• Present project kickoff slide deck by due date.
• Sign off of project charter.
• Sign off on CCB process.
• Kick off parallel processes:
  • Arch / Automated Testing.
  • Discovery.

Once the kickoff has been completed and the business requirements and goals have been set and agreed upon we begin working on designing the project. The requirements, overall design, and method for quality assurance over the lifecycle of the project start in the design process.

03 Design Process - CMMI RDM, TS

Our design process relies on the principles of user centered design. Discovery and Research phases are carried out to understand users and their needs, and the insights and findings obtained are used to create a tailored mission-critical requirements program. The design phase that follows builds up iteratively to render interface experiences that fulfill users and organization needs. The participation of users through usability testing and other activities within the iterative loops ensure curation and efficiency on the resulting product.

• Requirements
  • Conduct discovery sessions to obtain definitions:
    • Organization’s goals, Users goals
    • Define research activities and deliverables
  • Conduct research activities
    • Research Plan
    • Surveys or interviews
    • Competitive Analysis
    • Information Architecture
• Design solution to meet Requirements
  • UI Design plan
  • Conduct UI design activities
    • Product Flows
    • Wireframes
    • Design Mockups - iterative
    • Testing - Iterative
    • Style Guide - UI
    • Pattern Lab?
• Quality control
  • Quality control on implementation
  • Usability test - internal

Once the design process has been set up to deliver over the project’s lifetime. At this point we begin to build the framework that allows us to deliver on demand and that begins to take shape in our development process.

04 Development Process -
CMMI PR, TS, PI

Mobomo teams follow our standard CMMI Dev Level 3 / ISO 9001:2015 Agile Software Development Methodology for all of their products, employing “sprints” (time-boxing) - predetermined development cycles that run for two to six weeks (depending on client need and desired cadence).

User stories from each sprint are developed and implemented, running through the SDLC requirements, design, development, test, and implementation stage to deliver a functioning production-quality product at the end of each sprint cycle. These sprint iterations are refined every week, building on each other to hit each major milestone, and ultimately a launched product.

General process:

• Establish the product integration environment and product integration procedures and criteria
  • Development Environment
  • DevOps and Deployment
  • Source Code Management
• Work with design teams and project managers to develop sprint plans
  • Work with QA to develop functional tests
  • Develop features that meet requirements laid out in the project’s user stories
  • Conduct peer review and peer review analysis
    • Peer Review
  • Resolve issues identified during peer review
  • Develop, update, and maintain tech architecture document
    • Application Architecture
  • Develop, update, and maintain security process document
    • Security

At a certain point in the lifecycle of the project, the anticipation builds up, ticket velocity builds, and the teams see the launch date approaching. Agile Development is iterative by nature, so the next step in the process is not final but momentous.

05 Launch

Our launch process consists of going through each item specified during the kickoff and subsequent iterations of the project plan.

The launch process consists of reviewing content, enacting communication plan steps for each stage of the launch itself, ensuring performance benchmarks are met, reviewing compatibility on different platforms, ensuring accessibility requirements are met, determining infrastructure tasks are completed, setting baseline analytics for future measurement, and covering search engine optimization of htaccess and robots files.

• Configure CDNs
• Load testing
• Obtain / Configure SSL certificates
• Handle redirects
• Sitemap check
• Search indexes / stop words / etc
• Regression tests
• 3rd party integration tests
• RSS / Other feeds checks
• Obtain client approval for launch
• Necessary notifications (support teams)

One aspect of the launch process that is imperative and can make the difference between an easy launch and a difficult one is the testing process itself.

06 Testing Process - CMMI VV, RDM

Mobomo’s QA process revolves around early integration of our testing teams into the development cycle of a project and follows a 3-pillar approach of Manual Testing, Automated Testing, and Reporting. Our QA team works with business analysts and project managers to take requirements and create actionable test plans to follow throughout the course of the project.

It’s also important to develop tests accordingly and for developers to provide unit tests to ensure feature development integrates smoothly with the rest of the developed product. Projects are tested at every step of the SDLC to give customers confidence in our work and provide our own teams with peace of mind.

• Create a Test Plan during discovery phase
• Document and report testing outcomes on a regular basis
• Present metrics on testing practices
• Ensure quality of product by implementing quality control practices

Testing, design, and development all fall under the Project Management process itself. Accurate, dependable project management is key in keeping everyone on track, meeting deadlines, and using resources efficiently.

07 O&M

Operations and maintenance are not isolated from the rest of our process. Sometimes the unsung heroes are those maintaining legacy systems and continuing to meet business requirements. O&M is the bulk of most projects and, as such, much of our planning from a project standpoint is to simplify, speed up, and organize the O&M portion of each project.

What is O&M?

What gets covered in O&M or needs a change order:

• Determine best O&M management framework (Kanban vs. Scrum)
  • Following Agile Methodology, we assess the project to determine whether Kanban, Scrum, or ScrumBan is the best framework to manage the O&M work.
• Identify Scrum team - who are the members, how many?
  • All scrum teams will have a Certified Scrum Master (CSM), along with a team of engineers, QA, and DevOps. The team will also include UX and Content Strategists as needed.
• Identify Product Owners, UAT team on client side
  • In working with the client, we determine the Product Owner team who we’ll work with to write and validate tickets. The client Product Owner team will be involved in weekly meetings to review current Sprint status and plan future Sprint work. They will also be accountable for validating ticket details, along with UAT, when a ticket is completely Developed.
• Identify contract and project priority criteria. Are new fields required in JIRA?
• Establish estimation mechanism in JIRA (Story Points)
• Set clear expectations for JIRA tickets (description, personas, testing criteria, product owner)
• Set regular Sprint Planning meetings with key stakeholders per Sprint cadence

O&M cements Mobomo’s focus on customer satisfaction as it brings into sharp relief the focus we place on the details of each project. Part of our attention to detail comes from our excellent employees and their ability to push the envelope, seek out better ways to provide value, and continually invest in their own technical training and development.

08 Mobomo Culture of Excellence

At Mobomo, we hire ambitious self-starters. With that comes the responsibility to inspire them to push through comfort zones, learn new tech, and become thought leaders in their areas of expertise. Mobomo invests heavily in employee development by offering certification bounties, industry conferences, CSM certification, Mobomo Innovation Labs opportunities, as well as talent acquisition.

• Certification bounty: monetary reward for successfully achieving certifications
• Industry conferences: Open Source, emerging tech, industry, etc.
• (Virtual) Mobomo Day: Every Wednesday!
• CSM Certification: Every employee to Scrum Master Certification
• Mobomo Labs: Have a great idea? Get time to work on it!
• Talent Acquisition: Recruitment bonuses, opportunities, and retention

Our staff of full-time, dedicated experts in design, development, project management--along with our executive team--are focused on delivering on demand, on time, and within budget. We understand the nuances and idiosyncrasies that are involved with large-scale, web development projects. Our team is familiar with those intricacies and can speed up the process by avoiding roadblocks and pitfalls. We bring to bare multiple layers of expertise and innovation to get each project completed having met the business requirements and goals set by the customer.