Giving proposals/suggestions

4+
Intermediate
📙 Teens & Adults

Enhancing the ability to present proposals & suggestions clearly and persuasively in a software engineering work environment.

/

/

Giving proposals/suggestions

Part 1

Warm-up

💡 Directions

Answer the questions

Q1

What did we discuss in the last lesson?

Q2

Have you ever had to present/give a proposal/suggestion at work?

Q3

What challenges do you face when presenting/giving a proposal/suggestion?

Part 2

Vocabulary

💡 Directions

Read the word, its’ meaning, and the examples
Then make up your own sentences using the word.

Student can skip the words they already know.

groundbreaking

adjective

/ˈɡraʊndˌbreɪ.kɪŋ/

intuitive

adjective

/ɪnˈtuː.ɪ.tɪv/

perspective

noun

/pəˈspek.tɪv/

embrace

verb

/ɪmˈbreɪs/

alternative

noun or adjective

/ɑːlˈtɜr.nə.tɪv/

timeboxing

noun

/taɪmˌbɑksɪŋ/

NOTE

Make up your own sentences using the words.

Part 3

Reading comprehension and discussion

💡 Directions

Read the article and answer questions.

Teacher helps student correct their pronunciation.

The importance of proposals and suggestions in Software Engineering

In the dynamic field of software engineering, proposals and suggestions are vital tools for driving innovation, improving processes, and addressing challenges. Every member of the development team, including developers, DevOps engineers, product designers, IT business analysts, quality control (QC) specialists, product managers and so on… can contribute valuable ideas that help shape the future of a project or product.

Why proposals and suggestions are important:

  • Innovation: Proposals introduce new ideas and approaches that can lead to groundbreaking features or technologies.
  • Process improvement: Suggestions often highlight inefficiencies or problems in current workflows, leading to more streamlined and effective processes.
  • Problem solving: Proposals provide structured solutions to existing challenges, ensuring that issues are addressed systematically and thoroughly.
  • Team engagement: When everyone is encouraged to share their ideas, it fosters a collaborative and inclusive work environment.

Why everyone should give proposals:

  • Different viewpoints: Each role brings a unique perspective, which can lead to more comprehensive and effective solutions.
  • Empowerment: Allowing all team members to contribute ideas, it makes them feel important increasing job satisfaction and motivation.
  • Continuous improvement: Regular suggestions from all team members help keep processes and products getting better over time.

By embracing proposals and suggestions from all team members, software engineering teams can achieve greater innovation, efficiency, and overall success.

Check your understanding

Q1

Why are proposals and suggestions considered vital tools in software engineering?

Q2

How does encouraging everyone to give proposals contribute to team engagement?

Discussion

Q3

Can you give some examples of proposals and suggestions that team members can make?

Discussion

Q1

Is it more important to focus on new ideas or fixing current processes? Explain.

Ideas:

  • New ideas: innovation & growth, meeting market demands, enhanced creativity
  • Fixing current processes: efficiency & productivity, quality & reliability, customer satisfastion
Q2

Should proposals be submitted formally or informally? What are the benefits and drawbacks of each?

Ideas:

  • Formal: clear & structured, provides documentation, shows professionalism
  • Informal: Quick & easy, encourages participation, flexible.
Q3

Is it better to have a few detailed proposals or many quick ideas? Why?

Ideas:

  • Detailed: in-depth analysis, higher quality, easier to implement
  • Quick: encourages creativity, more options, faster innovation
Q4

What are the dangers of accepting too many proposals? How can these be avoided?

Ideas:

  • Overwhelm, loss of focus, poor quality, hard decisions, high costs
  • Avoid: set rules, prioritize, work together,…
Q5

Is it important to have a person or group in charge of reviewing proposals? Why?

Ideas:

Consistency, expertise, efficiency, quality control, prioritization

Q6

Should customer feedback be prioritized over team suggestions? Why?

Ideas:

  • Customer: direct insight, market relevance, customer satisfaction, revenue impact
  • Team: technical feasibility, innovation, efficiency, ownership
Q7

Are there types of proposals that should be avoided? If yes, which ones and why?

Ideas:

Unrealistic, redundant, low-impact, unclear, high-risk

Part 4

Useful phrases

💡 Directions

Teacher guides the student the useful phrases.

Useful phrases for proposals and suggestions in software engineering

Formal suggestions/proposals

When you are in a meeting with important clients or key members of your company, it is crucial to use formal language. Here are some formal expressions suited for making proposals in software engineering:

  • I propose that we…
    • Example: I propose that we migrate our application to a microservices architecture to improve scalability.
  • I suggest that we…
    • Example: I suggest that we implement a continuous integration pipeline to streamline our development process.
  • I advise we/you…
    • Example: I advise we conduct a thorough security audit to identify potential vulnerabilities.
  • I would recommend we…
    • Example: I would recommend we refactor the legacy code to enhance maintainability and performance.
  • I put forward that we…
    • Example: I put forward that we adopt automated testing to improve our test coverage and reduce manual effort.

Less formal suggestions

In less formal meetings with team members, suppliers, or customers with whom you have a good relationship, using less formal language can be more appropriate. Here are some expressions for making less formal suggestions in software engineering:

  • I think we should…
    • Example: I think we should look into using Docker for containerization to simplify our deployment process.
  • Why don’t we…?
    • Example: Why don’t we integrate customer feedback more regularly to ensure our features align with user needs?
  • How about…?
    • Example: How about we set up a sprint review meeting to track our progress more effectively?
  • What about…?
    • Example: What about using a new project management tool to improve our workflow?
  • We could try…
    • Example: We could try implementing pair programming to enhance code quality and team collaboration.
  • Let’s have a go at…
    • Example: Let’s have a go at using an A/B testing framework to optimize user experience.

Using these phrases appropriately can help you communicate your ideas effectively, regardless of the formality of the meeting.

💡 Directions

Students will practice making their own suggestions and proposals using the provided phrases

Exercise 1: Formal suggestions/proposals

Instructions: Use the following formal phrases to make a suggestion or proposal based on the given scenarios. Write one sentence for each scenario.

Student can choose only 2 scenarios to make the example.

  • I propose that we…
  • I suggest that we…
  • I advise we/you…
  • I would recommend we…
  • I put forward that we…

Scenarios:

  1. Scenario: The current project is experiencing frequent delays due to manual testing processes.

  2. Scenario: The product’s user interface is receiving negative feedback for being non-intuitive.

  3. Scenario: The company is considering expanding its product to a new market.

  4. Scenario: There is a need to improve team collaboration and communication.

Exercise 2: Less formal suggestions

Instructions: Use the following less formal phrases to make a suggestion based on the given scenarios. Write one sentence for each scenario.

Student can choose only 2 scenarios to make the example.

  • I think we should…
  • Why don’t we…?
  • How about…?
  • What about…?
  • We could try…
  • Let’s have a go at…

Scenarios:

  1. Scenario: The development team finds it challenging to track progress with the current project management tool.

  2. Scenario: There is a need to improve code quality and reduce bugs.

  3. Scenario: The sprint planning meetings are taking too long and not being productive.

  4. Scenario: The team wants to boost innovation and creativity.

Part 5

Debate

Topic: Should suggestions from senior members be more important than those from juniors? Why?

💡 Directions

In a debate on this topic, you need to talk about whether it’s important to learn some of the local language before going on a vacation. Say if you agree or disagree, give reasons, and use simple examples.

Preparation (3 minutes)

Student has 2-3 mins to think about their ideas.

Suggesting points:

  • Senior: More experience, knowledge of past projects, have vision, better in risk management
  • Junior: new ideas, up-to-date with trends, team dynamics,…

Debate (8 minutes)

Student has 2-4 mins to present their ideas.

Teacher helps student to expand their ideas, think critically & more views about this topic (by asking more questions about this topic).

Review

💡 Directions

Let’s review the lesson with teacher

1

New words in this lesson

2

The importance of proposals and suggestions in Software Engineering

3

Useful phrases for proposals and suggestions

See you next lesson

Homework

💡 Directions

Do homework

Write a sentence for each vocabulary today.

EnrichEnglish Teacher1