search
Enter at least two characters without personal information.

    LibraryArticles and FAQs Your projectRequest a quote
    LanguageEN ▾
    Methods and learning

    Web project management: responsibilities and practical exercise

    Project management makes scope, dependencies, responsibilities and delivery conditions explicit. It connects team decisions with required contributions and known risks. A schedule should show what enables a stage to start or finish, rather than only listing dates.

    These sheets describe activities and teaching exercises. They do not constitute job offers, certifying courses or recruitment promises.

    All job descriptions
    Illustration of design and review work on a computer
    AI-generated illustration

    Explore all 28 review cases — Two approvals contradict each other

    Missions and responsibilities

    Coordinate decisions, dependencies and approvals so the team shares a clear delivery scope and responsibilities beyond a launch date.

    Typical activities

    • Define scope, milestones and acceptance criteria.
    • Track content dependencies, blocking decisions and risks.
    • Organise acceptance, handover and change handling.

    Responsibilities to agree with the team

    Project managers coordinate rather than replace every specialist. Budget, acceptance and scope changes need identified owners; a schedule is not approval.

    A first piece of work to demonstrate

    Deliver a roadmap with dependencies, owners, pending decisions and a change-handling rule.

    This is an editorial description of common activities. Job titles and scope vary across teams; it is not a certification framework.

    W3C: organising accessibility responsibilities across a team

    Practice exercise

    Organize a redesign with missing content and integration into an existing tool.

    Work on a copy or demo environment. Define the data used and the expected result before you begin. Keep your decisions and the difficulties encountered in order to be able to explain the process.

    1. Describe deliverables, exclusions and validation criteria.
    2. Place the necessary contributions and decisions in the schedule.
    3. Maintain trade-offs and risks with a responsible person.
    4. Prepare functional validation and post-delivery transmission.

    Deliverable and checks

    Provide scope with exclusions, a schedule reflecting incoming content and a decision record. For the external integration, specify test access, the accountable contact and acceptance conditions. Link each risk to an action or pending decision.

    Simulate a delay to essential content and identify affected tasks, the decision owner and available options. Check that an added request explicitly changes scope or work order rather than disappearing behind an unchanged final date.

    Prepare website checks

    Risks and collaboration

    A schedule without delivery dates or decision makers masks dependencies. Delivery must have shared criteria.

    Collaboration to explore: quality assurance and functional validation.

    Fictional deliverable excerpt : Approval of booking conditions awaits an identified person; the open point and its effect on the next review are tracked.

    What passes between the roles : Product choices and delivery constraints are discussed with the team. In this example, priority and dependency are separate pieces of information; neither supports promising an unconfirmed date or feature.

    View the role comparison : Digital project manager and Product Owner →

    Employment, trades and training
    An example to examine

    Prepare a decision before moving a deadline

    Fictional teaching material: this excerpt illustrates part of a deliverable. It is not a client reference, a complete specification or evidence of professional qualification.

    Sample excerpt
    Dependency: approval of copy for three pages.
    Expected owner: named business representative.
    Effect: final implementation is waiting.
    Option A: approve all three pages by the agreed date.
    Option B: deliver a reduced scope with explicit acceptance.

    What the author should be able to explain

    1. The dependency is expressed as a decision to obtain.
    2. Ownership and its effect on subsequent work are visible.
    3. Reduced scope is not assumed to be accepted by default.
    Why not just change the date in the plan?

    A new date does not resolve the dependency. Confirm the decision, affected content and consequences for other steps, then update the shared plan.

    Assess the quality of the work

    For the exercise, essential publication content arrives late while a new request is added. Project coordination should expose decisions and their effects on remaining work. Examine deliverables, dependencies and responsibilities: retaining a date in a plan does not explain how the team can still achieve it.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Assess the quality of the work
    SkillEvidence to examineFailure to spot
    Deliverable and acceptanceDescribe the intended result, exclusions, approver and evidence needed for their decision. Separate started work, completed checks and accepted results.A task closes because a file was delivered although required content is absent or nobody approved its use.
    Dependency and decisionIdentify essential inputs, owners, useful dates and blocked activities. Prepare options if an input is unavailable.A delay remains a note without changing work order, or someone is assigned responsibility for approval they cannot provide.
    ChangeEffects on time, cost and quality are exposed before deciding.An added request changes neither priorities nor planned capacity.
    Blocking decisionName the required decision, owner, deadline and dependent deliverables.A delayed approval leads to an explicit scope or schedule decision instead of remaining buried in meeting notes.

    A focused next step

    Introduce the delay into a fictional plan and compare reducing scope, moving a stage or obtaining the missing input. Specify decision ownership and which result needs rechecking. After the decision, ensure the team and approver share the same scope and publication conditions.

    W3C WAI: planning and managing accessibility. · Source consulted

    Documented reference points for this topic

    Documented reference points for this topic
    ReferenceValue or syntaxScope
    WCAG 2.2 · 2.5.8
    24 × 24 CSS pxA smaller target can satisfy the criterion through spacing; other exceptions apply.
    Google Search · Sitemap
    50 000 URL · 50 MBLimits per uncompressed file; larger sets require several sitemaps.
    WordPress · Tools Export
    WXR / XMLA WordPress content export can include posts, pages, post types, comments, custom fields and taxonomies. Its scope depends on selected filters. Check media files, theme, plugins and configuration separately before treating it as a complete migration.

    Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.

    A review case to reproduce

    Two approvals contradict each other

    Situation to examine
    Two people approve different versions of one deliverable. The released file cannot be connected to a clear decision.
    Proposed check
    Find version, date, scope and authorised decision owner. Consolidate feedback into one decision and inspect affected dependencies. Explain how later changes reopen approval.
    Evidence to retain
    A decision log connects the delivered version to approval. Open questions have owners and explicit next steps.
    Fictional finding example
    The authorised person approves V3. V4 is prepared from another comment, but delivery mixes V3 copy and V4 artwork.
    Interpret this outcome
    Link delivery to a complete version and its decision. Partial approval does not automatically cover a later variation.

    Three complementary checks

    Fictional cases: adapt these expectations to your test contract and retain the limits of the check.

    1. Bounded version
    2. Explicit decision
    3. Reconciled delivery

    Scroll the table horizontally if needed; with a keyboard, focus it and use the arrow keys.

    Scenario variations and expected evidence
    Variation to testExpected result in this caseEvidence to hand over
    Only part is approvedLimit approval to its stated scopeList of actually approved elements
    V3 and V4 contain different feedbackAvoid combining them without a decisionDecision covering one complete version
    Scope changes after approvalReopen affected points and dependenciesChange request and updated approvals

    Decision to hand over : Link the handed-over deliverable to a complete, dated and attributed decision.

    Method reference : W3C WAI — Planning and Managing

    Learning scenario

    Extended exercise and expected deliverables

    In-depth exercise: Organize the redesign of a service page with writing, translation, photo and integration. Build a list of dependencies before putting dates. Simulate a validation delay and scope change. Describe the decisions needed to maintain a useful deliverable. A schedule is not proof of availability: indicate the hypotheses, the people responsible and the points that can block the publication.

    What to deliver with your work

    • Scope, deliverables and acceptance criteria
    • Dependencies and decision makers
    • Planning with explicit hypotheses
    • Changes and risks log tracked

    Acceptance criteria

    These criteria are a working basis to adapt to the context. For each, note the action taken, the expected result, the observed result and the information remaining to be confirmed.

    1. Each deliverable has a person who can validate it.
    2. A blocking dependency appears before the delivery date.
    3. A change of scope specifies its effect on the planned work.
    4. Functional validation and fault recovery are included in the delivery process.

    Understand pre-launch checks

    Ongoing management and handover

    Share the scope, decisions and open risks in a format that the team can follow. A useful meeting produces an arbitration, an official, or a next action, not just a report. When handing over, explain the constraints that led to the schedule. After delivery, keep the decisions that will be used to maintain the site and understand its changes.

    Organize site maintenance

    Compare two approaches

    Project management makes decisions and dependencies visible. Compare delivery with a fixed scope against incremental progress according to project uncertainty.

    Defined scope and milestones

    When to choose it
    Suitable when deliverables and approvals are known. Specify content, owners and conditions needed for each milestone.
    What to plan for
    Plan change requests. A schedule without available sources, translations or approvals remains a hypothesis.

    Verifiable incremental deliveries

    When to choose it
    Useful when needs become clearer during implementation. Define a usable outcome and the decisions expected at each stage.
    What to plan for
    Keep sight of the complete workflow and its dependencies. Successive small tasks do not guarantee coherent delivery.

    A risk to anticipate

    Do not confuse started work with accepted results. Editorial and business blockers must be as visible as technical blockers.

    How to decide

    Prepare the next decision with alternatives, constraints and owners. The record should distinguish decisions from matters still awaiting confirmation.

    Explore this decision further

    Compare scope and costs

    Setup
    Compare scope, dependencies and decisions actually supported. A schedule differs from coordination including owners, exit criteria and risk tracking.
    Recurring operation
    Define follow-up cadence and change handling. Separate planned coordination from scope expansion; record decisions affecting workload and responsibility.
    Exit and handover
    Request restart status, open decisions and deliverable links. Handover must allow continued work without oral explanations or confusion between planned and finished.

    Compare the costs of three web solutions

    Frequently asked questions

    How can a blocker be exposed without adding meetings?

    Give it a required decision, an owner and a deadline relevant to the schedule. Distinguish work started, reviewed output and accepted output. A short check-in helps when it resolves a specific dependency; a progress percentage without a deliverable is insufficient.

    What should happen when a request arrives after scope approval?

    Describe the need and its effect on tasks, content, schedule and cost. Offer options: replace a priority, defer it or extend the scope. The authorised person decides before the team treats the addition as an accepted commitment.

    How should a request added during a project be handled?

    Describe the need and its effects on scope and dependencies. Compare immediate addition, replacement and postponement. Obtain approval for consequences on deliverables and checks; avoid silently adding it to the schedule.

    Further reading

    Browse other resources