Skip to main content

TocToc

Menu
Client Login

TOCTOC PLAYBOOK

Welcome to TocToc’s Digital Marketing Playbook, where transparency comes first. We’re upfront because we value your trust. Our goal is to help you invest wisely and get the results you want. With us, your projects, time, and money are in safe hands. This PlayBook gives you a quick look at how we operate.

Requirements Analysis:
A Comprehensive Overview for TocToc

Introduction to Requirements Analysis

At TocToc, requirements analysis is a fundamental phase in project development, focusing on understanding client needs. This process is essential for defining project scope, timeline, and quality. Our approach to requirements analysis consists of several stages:

  1. Gathering and Analysing Client Requirements
  2. Documenting Requirements
  3. Project Estimation

The key team members involved in this phase typically include the Project Manager (PM), Designer, Team Lead, and Developers. Their collaborative efforts are crucial for transforming client visions into actionable project plans.

Gathering and Analysing Client Requirements

Importance of Requirement Gathering

Gathering and analysing client requirements is crucial for project success, directly impacting quality and duration. Clear requirements reduce risks like missed deadlines and scope creep. At TocToc, we prioritise clarity and completeness to ensure all stakeholders share a common understanding.

Types of Requirements

Client requirements are categorised into two main types:

  1. Functional Requirements: Specify what the system should do, detailing user interactions and system responses.
  2. Non-Functional Requirements: Define how the system should perform, addressing quality attributes like performance, usability, and reliability.
 Methods of Gathering Requirements

To effectively gather requirements, TocToc employs several techniques, including:

  • Questionnaires and Surveys: Collect structured information from clients.
  • Interviews: Facilitate deeper understanding through direct communication.
  • Document Analysis: Review existing documentation to extract relevant insights.
  • Brainstorming: Encourage collaborative idea generation.
  • Prototyping: Enable stakeholders to visualise requirements.
Skills Required for Successful Requirements Gathering

The PM at TocToc must possess a diverse skill set, including:

  • Subject knowledge
  • Active listening and effective questioning
  • Team collaboration and conflict resolution
  • Stress resistance and analytical capabilities
  • Creativity in problem-solving

Requirements Documenting

After gathering and analysing client requirements, the next step is documentation. This stage ensures that all stakeholders have a clear understanding of project requirements.

Requirements List (RL)

Documented requirements are compiled into a Requirements List (RL). While ideally prepared by the project team, TocToc often works with existing RLs provided by clients.

Documentation Approaches

Documentation can take various forms, depending on project size:

  • Software Requirements Specification (SRS): Comprehensive documentation for large projects.
  • Feature Descriptions in Word Documents: More flexible documentation for smaller projects.
  • Internal Specifications: Tailored documentation that supports development and testing processes.

All documentation must be stored in accessible formats, updated regularly, and linked within project management tools like Redmine.

Project Estimation

Following documentation, requirements are passed to the development team for estimation, led by the PM to ensure accuracy.

Estimation Process

The estimation phase involves analysing documented requirements to create a project quote, outlining costs and timelines. This process includes:

  • Using Redmine for Tracking Estimates: A dedicated section in Redmine is reserved for quotes.
  • Collaborating with Developers and Designers: Their insights are essential for accurate estimations.

The result of this phase is a detailed XLS file outlining costs and timelines, discussed with the client.

Types of Client Requirements

Functional requirements can be further categorised into:

  • Business Requirements: Define features from a business perspective.
  • User Requirements: Focus on end-users’ needs, often detailed in use cases.
  • System Requirements: Outline technical specifications, such as hardware and software requirements.
  • Functionality Requirements: Describe operational aspects of the software.

Non-functional requirements include:

  • Business Rules: Guidelines governing the system’s functionality.
  • External Interfaces: Describe interactions with external systems.
  • Quality Requirements: Focus on system attributes like performance and usability.
  • Development Constraints: Consider limitations such as budget, time, and resource availability.
Methods of Obtaining Client Requirements

The process begins with gathering input data, which encompasses:

  • Client ideas and vision
  • Specific project tasks
  • Stakeholder insights

Key participants in the requirements gathering process include the PM, Team Lead, Development Team, and Client Representatives.

The ultimate goal is to compile comprehensive client requirements, documented as notes, audio recordings, or mockups.

Techniques for Effective Requirements Gathering

TocToc utilises various techniques suggested by the PMBOK Guide for effective requirements gathering, including:

  • Interviews: For acquiring detailed information.
  • Focus Groups: Facilitate collaborative input from multiple stakeholders.
  • Workshops: Structured meetings for brainstorming.
  • Prototyping: Developing preliminary versions to gather feedback.

Specific techniques include:

  • Questionnaires: Surveys with open and closed questions to confirm or refine requirements.
  • Interviews: Structured discussions to delve deeper into client needs.
  • Brainstorming: A creative approach for rapid idea sharing among stakeholders.

Combining these methods enhances the efficiency of requirements gathering and reduces the risk of overlooking critical information.

Documentation of Client Requirements

Once the information is gathered, the PM must ensure meticulous documentation of all requirements.

Documentation Process

The documentation process includes:

  1. Creating the Requirements List (RL) from gathered data.
  2. Ensuring stakeholder access to this documentation.
  3. Regularly updating the RL based on feedback and project evolution.
Principles for Requirements Documentation

Key principles guiding TocToc’s requirements documentation include:

  • Clarity and Completeness: All requirements should be well-defined.
  • Version Control: Maintain a history for tracking changes.
  • Accessibility: Documentation should be easily navigable for both internal teams and clients.
Types of Requirements Documentation

At TocToc, we use different types of documentation based on project needs:

  • SRS (Software Requirements Specification): Comprehensive for large projects.
  • Word Document Feature Descriptions: Flexible and informal for smaller projects.
  • Internal Specifications: Used actively in the development process.

Project Estimation Overview

Project estimation is crucial for assessing the scope, timelines, and costs of a project based on client requirements. At TocToc, key participants include the PM, Team Lead, and Developers, who work together to ensure accurate estimates.

Steps in Project Estimation

  1. Creating a Quote:

    • The PM creates a task in Redmine that includes a comprehensive project description and relevant documents.
    • The development team reviews the information and clarifies project details through discussions.
    • The project is broken down into manageable components, each estimated by developers.

  2. Preparing a Commercial Proposal (CP):

    • After the initial quote, the client receives an Excel file outlining tasks and estimated hours.

    • The client reviews this estimation with the PM to finalise the project budget.

    • Once approved, the PM prepares the Commercial Proposal, which includes:

    • Project Overview: Description of the project and objectives.

    • Platform and Technical Solutions: Information on chosen technologies.

    • Scope of Work: Detailed outline of services provided.

    • Cost and Payment Terms: Financial documentation, including payment models and conditions.

    • Post-Launch Support: Details regarding support after project completion.

    • About Us Section: Brief introduction to TocToc, highlighting our competitive advantages.

Final Details

The proposal concludes with the date and the Director’s stamp and signature to formalise the document.

Project Planning

Introduction to Project Planning

Once project specifications are finalised and the client approves the estimate, the project moves into the Planning and Development stage, which consists of:

  1. Project Planning
  2. Project Development
  3. Technical Support
Key Participants in Project Planning

Key participants at TocToc during this phase include the PM, Designer, Team Lead, Development Team, Tester, Client, and CTO. Coordination and decision-making are managed by leading department managers.

Importance of Planning

Planning is essential for establishing project success criteria—scope, time, and quality. This phase involves setting up infrastructure and technical support before development begins, overseen by the PM.

Key Highlights of Project Planning
  • Checklist Usage: The PM utilises a checklist to ensure all elements are covered.
  • Timeline: A critical tool for resource allocation and work evaluation.
  • Primary Infrastructure: Tools like Redmine and Bitbucket are used for project management.
  • Communication Tools: Team communication occurs via Skype, Slack, and email.
Redmine Capabilities

Redmine offers essential project management capabilities, including:

  • Task creation and monitoring.
  • Risk assessment and efficiency calculations.
  • Centralised information storage.
  • Connection to external users.

Project Development

Overview of Development

The development phase is critical, validating resource planning and timelines while allowing clients to see tangible results. The PM oversees team performance, timelines, resources, quality, costs, and client feedback.

Development Process
  1. Initial Team Meeting:
    • Discuss project details and confirm task estimations.
    • Determine technical solutions and architecture.
    • Agree on future meeting frequencies.
  2. Task and Phase Structure:
    • Tasks are the smallest units of project functionality.
    • Phases consist of logically linked tasks with specific deadlines.
    • Intermediate results are presented to the client after completing phases.
  3. Quality Assurance:
    • Completed tasks undergo testing by designated QA testers.
    • Adherence to the approved Requirements List (RL) is crucial to prevent changes in terms or payments.
  4. Final Phase Preparation:
    • Analyse current project status, client history, and future needs.
    • Suggest improvements before finalising the project for deployment.
  5. Project Completion Obligations:
    • Conduct retrospective analysis after project completion.
    • Document the project for the company’s portfolio.

Technical Support for Websites at TocToc

At TocToc, our technical support is essential for maintaining a website’s functionality, ensuring it operates smoothly and without issues. We cater to both internal clients, for whom we build sites from scratch, and external clients with existing websites.

Participants in this process include the Project Manager, Client, Team Leads, Developers, and Testers. Outcomes focus on achieving a fully functional website, adhering to the client’s budget, and managing planned workloads for developers. We offer two types of website support:
  1. Technical Support:
    • Website Audits: Identifying technical issues, checking load speeds, and ensuring mobile compatibility. We fix obvious bugs and propose solutions.
    • Website Updates: Implementing redesigns, adding new pages, and installing modules as needed.
    • Functionality Support: Regular backups, error corrections, and virus scans.
    • Hosting Interaction: Managing server transfers, backups, and domain changes.
  2. Informational Support:
    • Involves updating content (text, images, videos) and assisting with SEO.

Support can be on-demand for specific issues or ongoing with a set monthly hour plan. This holistic approach at TocToc ensures that our clients’ websites remain up-to-date and effective.