2.3 Meetings — Agenda, Minutes & Planning
What is a Meeting?
A meeting is a planned gathering of two or more people, in person or virtual, to discuss, decide, plan or coordinate on specific matters.
The textbook definition: "A meeting is an assembly of people for a specific purpose, usually involving formal or semi-formal discussion to reach decisions or share information."
Why meetings exist
| Purpose | Example |
|---|---|
| Information sharing | Weekly team status update |
| Decision making | Whether to approve a vendor |
| Problem solving | Root-cause analysis of a production outage |
| Planning | Sprint planning, project kick-off |
| Brainstorming | Generating ideas for a campaign |
| Coordination | Aligning multiple teams on a release |
| Negotiation | Vendor contract discussions |
| Approvals | Senior management sign-offs |
| Training | Onboarding new hires |
| Team building | Quarterly reviews, off-sites |
---
Kinds of Meetings
Meetings differ by formality, purpose, and participant level:
| Kind | Description | Example |
|---|---|---|
| Formal meetings | Pre-scheduled, with agenda, minutes, formal structure | Board meeting, AGM |
| Informal meetings | Quick, ad-hoc, no formal minutes | Coffee-room sync, corridor chat |
| Statutory meetings | Required by law (Companies Act) | First-year AGM of a public company |
| Annual General Meeting (AGM) | Yearly shareholder meeting | Reliance, TCS, Infosys AGMs |
| Extraordinary General Meeting (EGM) | Urgent shareholder meeting | Outside the regular calendar |
| Board meetings | Board of directors | Quarterly board reviews |
| Committee meetings | Sub-group of larger body | Audit committee, technical committee |
| Departmental meetings | One department's team | Weekly engineering sync |
| Inter-departmental | Across departments | Engineering + Marketing alignment |
| Town-hall meetings | Whole company / large group | Quarterly CEO town hall |
| Standing meetings | Recurring (daily, weekly) | Daily stand-up, weekly review |
| One-on-one (1:1) | Manager-direct report | Weekly manager-employee sync |
| Brainstorming meetings | Idea generation | Product ideation, design jam |
| Project meetings | Specific project | Kick-off, status, retrospective |
| Virtual / Hybrid meetings | Video or mixed | Zoom team calls, Teams meetings |
---
Planning and Organising a Meeting
A poorly-planned meeting wastes the time of every participant — multiplied by headcount. A 1-hour meeting with 8 people consumes 8 person-hours. Plan well.
Step-by-step planning checklist
| Step | Action |
|---|---|
| 1. Purpose | Define why the meeting is needed. Can it be replaced by an email? |
| 2. Outcomes | What concrete decisions or actions should result? |
| 3. Participants | Who must attend? Who only needs to be informed? |
| 4. Date and time | Check participant calendars; allow notice |
| 5. Venue / link | Room booking; or Zoom / Teams link |
| 6. Agenda | List of topics with time allocations (see below) |
| 7. Pre-reads | Background docs sent in advance |
| 8. Chair / Moderator | Who runs the meeting |
| 9. Note-taker | Who records the minutes |
| 10. Equipment | Projector, speakers, whiteboard, snacks |
| 11. Invitations | Send 3-5 days in advance for formal meetings |
| 12. RSVP tracking | Confirm attendance |
Sample meeting invitation
Subject: Project Sprint Review — Friday 28 May, 3:00 PM Hi all, You are invited to the Sprint-7 review for Project Phoenix. Date: Friday, 28 May 2026 Time: 3:00 - 4:30 PM IST Venue: Conference Room B (and Zoom link for remote: bit.ly/sprintreview) Agenda attached. Please review the demo build (link in calendar invite) before the meeting. Action requested: Confirm attendance by EOD Wednesday. Thanks, Priya Sharma Project Manager +91 98765 43210
---
Agenda
The agenda is a written outline of topics to be discussed at the meeting, in the order they will be addressed.
Why an agenda matters
- Sets expectations — participants know what's coming
- Keeps the meeting focused — chair refers to agenda when discussion drifts
- Allocates time — prevents one topic eating the whole meeting
- Enables preparation — participants know what to read / think about
- Becomes a permanent record — attaches to minutes
Standard agenda format
AGENDA
Project Phoenix Sprint Review
Date: 28 May 2026 | Time: 3:00–4:30 PM
Venue: Conference Room B / Zoom
Chair: Priya Sharma
1. Welcome and roll-call 3:00 – 3:05 PM
2. Adoption of previous meeting minutes 3:05 – 3:10 PM
3. Sprint demo 3:10 – 3:40 PM
3.1 Team A demo
3.2 Team B demo
4. Sprint retrospective 3:40 – 4:00 PM
5. Sprint planning for Sprint 8 4:00 – 4:20 PM
6. Any Other Business (AOB) 4:20 – 4:25 PM
7. Confirmation of next meeting date 4:25 – 4:30 PM
Pre-read: Sprint-7 burndown chart (attached).
Standard agenda items
| Item | When |
|---|---|
| Welcome / Roll call | Always first |
| Adoption of previous minutes | If there were earlier meetings |
| Action items from last meeting | Status check |
| Main agenda topics | Allocated time each |
| Reports | From sub-committees, leads |
| New business | Items raised in this meeting |
| Any Other Business (AOB) | Catch-all for last-minute items |
| Date of next meeting | Schedule before everyone leaves |
---
Minutes of the Meeting (MoM)
Minutes are the written record of what was discussed and decided during a meeting. They are an official document — referenced later, used to track action items, and required for legal compliance in board / AGM meetings.
What minutes capture
| Section | Content |
|---|---|
| Header | Meeting name, date, time, venue, type (regular / special) |
| Attendees | Names of participants; apologies from absentees |
| Chair / Note-taker | Who chaired; who took minutes |
| Approval of previous minutes | Status |
| Topic-wise discussion summary | Each agenda item, key points, who spoke (selectively) |
| Decisions taken | Clearly noted with motion/proposer if formal |
| Action items | Who does what by when |
| Date of next meeting | If decided |
| Signature of chair | Final approval |
Sample Minutes
MINUTES OF SPRINT-7 REVIEW MEETING
Date: 28 May 2026 | Time: 3:00 – 4:30 PM
Venue: Conference Room B + Zoom
Chair: Priya Sharma
Minutes by: Rohan Mehta
Present:
- Priya Sharma (Project Manager) [Chair]
- Rohan Mehta (Team Lead — Team A)
- Anjali Verma (Team Lead — Team B)
- 5 other team members (full list in appendix)
Absent with apology: Vikram Singh (on leave)
1. Welcome
Priya welcomed everyone and called the meeting to order at 3:00 PM.
2. Previous minutes
Minutes of Sprint-6 review (held 14 May 2026) were approved without
amendments. Proposed by Rohan, seconded by Anjali.
3. Sprint demo
3.1 Team A demoed the new login flow with OTP integration.
No defects reported. Customer demo scheduled for 5 June.
3.2 Team B demoed the dashboard analytics module.
2 minor UI issues flagged; to be fixed before customer demo.
4. Sprint retrospective
- What went well: pair-programming reduced bug count by 40%
- What didn't: deployment to staging took 2 days (target: 1 day)
- Action: investigate staging-deploy bottleneck (Rohan, by 2 June)
5. Sprint-8 planning
Sprint-8 will run 1–14 June 2026.
Stories prioritised:
- Payment gateway integration (Team A)
- Notification system (Team B)
- Performance testing (joint)
6. AOB
Anjali raised that the testing environment crashes every Monday
morning. IT team to be looped in (Action: Priya, by 30 May).
7. Next meeting
Sprint-8 review: 14 June 2026, 3:00 PM, Conference Room B.
Meeting closed at 4:28 PM.
Action Items Summary:
─────────────────────────────────────────────────────
No. | Action | Owner | Due
─────────────────────────────────────────────────────
1 | Fix Team B UI issues | Anjali | 4 Jun
2 | Investigate staging-deploy | Rohan | 2 Jun
3 | Loop in IT for env crashes | Priya | 30 May
─────────────────────────────────────────────────────
Signed: ______________________
Priya Sharma (Chair)
Date: 28 May 2026
Rules for good minutes
| Rule | Why |
|---|---|
| Take notes in real time — write up later | Memory fades fast |
| Capture decisions, not debates | The record is for action, not transcripts |
| Use names sparingly | Focus on agreed outcomes |
| Be objective | No opinions in minutes |
| Action items must include owner + due date | Else they don't happen |
| Distribute within 24 hours | While context is fresh |
| Get chair's sign-off before final distribution | Authenticity |
| Archive systematically | Searchable, dated, named |
---
Conducting a Meeting — Tips for the Chair
Before
- Send agenda 2-3 days in advance
- Confirm logistics
- Pre-read all documents
During
- Start on time — even if some are late
- Welcome + roll call
- State meeting purpose in 1 sentence
- Follow the agenda — don't let it drift
- Manage time — gentle interruption if a topic runs over
- Encourage participation — call on quiet members
- Control dominators — gently bring them down
- Summarise decisions before moving on
- Capture action items with owners and due dates
- End on or before time — and don't add new topics at the end
- Thank everyone
After
- Distribute minutes within 24 hours
- Follow up on action items
- Confirm next meeting
---
Advantages and Disadvantages of Meetings
Advantages
| Advantage | Detail |
|---|---|
| Brainstorming power | Multiple perspectives find better solutions |
| Faster decisions | Easier to align in person |
| Builds team bonds | Face-to-face strengthens relationships |
| Knowledge sharing | Different experts in one room |
| Clear accountability | Action items assigned publicly |
| Two-way communication | Immediate questions and clarifications |
| Commitment | Public commitments are more likely kept |
Disadvantages
| Disadvantage | Detail |
|---|---|
| Time-consuming | 1 hr × 10 people = 10 person-hours |
| Costly | Multiplied by salaries, this is significant |
| Often unfocused | Drift without strong chair |
| Dominated by extroverts | Introverts under-contribute |
| Decision delay | Some topics need deeper analysis |
| "Meeting culture" trap | Companies that meet about meetings |
| Status not work | Meetings about work ≠ doing work |
| Pressure to agree publicly | Real concerns surface in corridor |
When NOT to have a meeting
- Sharing information that fits in an email
- Decisions only one person needs to make
- Routine updates (use async tools)
- Status that a dashboard already shows
- Reactions to a doc — let people read it first
---
Modern Meeting Practices
| Practice | Where Used |
|---|---|
| Stand-up meetings | Daily 15-minute sync — Agile teams |
| Async meetings | Loom video updates instead of live sync |
| No-meeting days | "Maker mode" days at Asana, Atlassian, others |
| Meeting-free hours | Block 2-3 hours daily for deep work |
| DACI / RACI in agendas | Each item flagged Driver / Approver / Contributor / Informed |
| Walking meetings | 1:1s done while walking |
| Hybrid-friendly defaults | Camera-on policy, equal voice for remote |
---
Study deep
- Most meetings could be an email. A 2018 survey by Atlassian found professionals waste ~31 hours/month in unnecessary meetings. The discipline: every meeting needs a clear purpose, agenda, and outcome — else cancel.
- Minutes are legal documents. For board meetings, AGMs and statutory bodies, minutes have legal weight under the Companies Act. They are read in audits, lawsuits, and shareholder challenges. Casual phrasing in minutes can cause real damage.
- The chair sets meeting culture. A weak chair → meetings drift, dominators dominate, decisions don't happen. A strong chair → focused, fair, productive.
- Action items without owners + dates are decoration. "Someone should look at X" doesn't get done. "Rohan to investigate X by 2 June" gets done. Always assign owner + date.
- The 6 Ps of meetings — Proper Prior Planning Prevents Poor Performance. A meeting prepared 30 minutes in advance is dramatically more productive than one walked into cold.
Key Terms — Lesson 2.3
The terms below cover meeting vocabulary — every PYQ on agenda, minutes, or meeting planning expects fluent use.
Meeting — A scheduled gathering of two or more people to discuss, decide, or share information. The most common form of structured organisational communication. Differs from a casual conversation by having a declared purpose, identified attendees, and an expected outcome.
Types of Meetings — Common categories: information-sharing (briefings, updates), decision-making (where a vote or call is required), brainstorming (idea generation, no immediate decision), problem-solving (root-cause + plan), status / stand-up (recurring short check-ins), planning (sprint planning, roadmap), review (postmortem, retrospective), ceremonial (AGM, annual review).
Annual General Meeting (AGM) — A statutory yearly meeting of a company's shareholders required by the Companies Act in India and similar laws elsewhere. Covers presentation of accounts, appointment of auditors, declaration of dividend, and election/re-election of directors. AGM minutes are legally significant.
Extraordinary General Meeting (EGM) — A shareholder meeting called between AGMs to handle urgent business — usually requested by the board or by shareholders holding a specified minimum stake. Reserved for time-sensitive matters that cannot wait for the next AGM.
Board Meeting — A meeting of a company's board of directors. Less frequent than operational meetings but legally and strategically significant. Decisions taken at board meetings often have legal weight; minutes are scrutinised by auditors.
Stand-up Meeting / Daily Scrum — A brief (15-minute), daily, often literally standing team check-in. Each person answers three questions: What did I do yesterday? What will I do today? What is blocking me? Standing keeps it short. Used by Agile/Scrum teams worldwide.
Stakeholder — A person or group with interest in the meeting's outcome — direct attendees plus others who care about the decisions. Not every stakeholder needs to attend; some receive minutes only.
Chair / Chairperson — The person who runs the meeting — sets the agenda, calls participants, manages time, ensures every voice is heard, guides the meeting toward decisions, formally closes. The chair sets the culture of the meeting.
Secretary (of the Meeting) — The person who records the meeting — takes notes, drafts the minutes, distributes them after. In formal meetings, the secretary is named in the minutes and may be the company secretary.
Notice (of Meeting) — The formal advance announcement of a meeting, sent to all attendees. Specifies date, time, venue (or video link), and agenda. For statutory meetings (AGMs, board meetings), the notice has legally mandated minimum periods (e.g., 21 clear days for AGM).
Agenda — A structured list of topics to be discussed at the meeting, in the planned order, often with time allocations and the responsible person per item. Circulated with the notice; allows attendees to prepare. A good agenda turns a vague gathering into a focused meeting.
Minutes of Meeting (MoM) — The official written record of what happened at a meeting — attendees, decisions made, action items, key points raised. Drafted by the secretary, approved at the start of the next meeting. The standard reference document for "what was agreed."
Quorum — The minimum number of attendees required for a meeting to make valid decisions. Defined by the organisation's bylaws or law (e.g., Companies Act specifies quorum for AGMs and board meetings). Decisions taken without quorum are invalid.
Proxy — A person authorised to attend and vote on behalf of an absent member. Common at AGMs where shareholders cannot attend in person. The proxy is registered in advance; their vote counts as the member's.
Resolution — A formal proposal voted on at a meeting — "Resolved that the company appoints XYZ as auditors for FY 2025–26." Resolutions are recorded in minutes with the result (passed/rejected, votes for/against).
Action Item — A specific task assigned in a meeting, with an owner and due date. "Rohan to investigate API timeout by 2 June." Action items without owner and date rarely get done. The single most important output of most meetings.
Owner / Action Owner — The named person responsible for completing an action item. Distributing responsibility ("the team will look into it") almost guarantees nothing happens.
Due Date / Target Date — The deadline by which an action item should be completed. Without a date, the action drifts. Optimistic dates are better than no dates; over-promises get re-set in the next meeting.
Tabled — A motion or topic that is set aside for discussion at a later meeting rather than addressed now. Used when more information is needed, when the right people are absent, or when time has run out.
Off the Record — A note that a particular point is not to be recorded in minutes. Used for sensitive personnel discussions, legal speculation, or candid feedback. The phrase carries weight in formal meetings; modern minutes still typically note that an off-the-record discussion occurred.
RACI / DACI Matrix — A responsibility-assignment framework often used in meeting agendas and action items. RACI: Responsible (does the work), Accountable (signs off), Consulted (input sought), Informed (kept aware). DACI: Driver, Approver, Contributors, Informed — a variant used for decisions.
Async Meeting — A meeting conducted without everyone being live at the same time — typically via a recorded video update (Loom), a written document, or a Slack thread. Modern remote teams substitute many "could have been an email" meetings with async updates.
No-Meeting Day / Maker Day — A practice (Asana, Atlassian, Google) where one day a week is declared meeting-free so engineers and designers have uninterrupted blocks for deep work. Recognises that meetings, however useful, fragment focus.
Hybrid Meeting — A meeting with some attendees in person and some remote. Requires deliberate practices to give the remote participants equal voice — camera on for everyone, written-chat acknowledgement, rotating speaking order.
Meeting Culture — The organisational norms around meetings — how often, how long, how many participants, who speaks, whether decisions get made. Strong meeting cultures default to clear purpose + clear outcome; weak cultures default to recurring meetings nobody questions.
Postmortem / Retrospective — A specific meeting type after an incident or sprint — what happened, what went well, what didn't, what we change. Modern best practice: blameless — focus on system improvements rather than individual fault.
Read-Ahead / Pre-Read — Material circulated in advance of a meeting for attendees to read, so meeting time can be spent on discussion rather than presentation. The Amazon "six-page memo" is the famous example.
Brainstorming — A meeting format aimed at generating many ideas without immediate judgement. Rules (Alex Osborn, 1953): defer judgement, go for quantity, build on others' ideas, encourage wild ideas. Convergence to a decision happens after brainstorming, not during.
---
Common exam question (very high frequency): "What is an agenda? What is minutes of meeting? Explain with format." — Define both; show sample agenda (with topics + time + chair); show sample minutes (with header + present + decisions + action items + signature).
Common exam question: "Discuss the planning and organisation of a meeting." — 10-12 step checklist from purpose → outcomes → participants → invitations.
Common exam question: "Advantages and disadvantages of meetings." — 5-6 each in a table; close with "modern alternatives: async, stand-ups, no-meeting days".
Self-check
Five quick checks on agenda, minutes, and meeting discipline.
- What must circulate before a meeting so attendees prepare? (the agenda)
- List four things minutes must record. (attendees/present; decisions; action items; who-by-when)
- What does the abbreviation MoM stand for? (Minutes of the Meeting)
- Name two modern alternatives to a live meeting. (async update; no-meeting / maker day)
- State two of Osborn's brainstorming rules. (defer judgement; go for quantity; build on others' ideas; encourage wild ideas)
- What is a "read-ahead" or pre-read? (material circulated in advance so meeting time is spent on discussion, not presentation)