CodeYourFuture / CodeYourFuture/Module-Data-Groups

Make a business proposal to take a risk

Open
#12 0 comments 0 reactions 0 assignees View on GitHub
🏝️ Priority Stretch 🐂 Size Medium 📅 Sprint 2 Module-Data-Groups Optional Submit:Slack
Dominant language
JavaScript
Stars
1
Forks
326
Avg merge
3h 25m
Merged PRs (30d)
2

Description

### Learning Objectives

- [ ] Practice writing a business proposal

### Why are we doing this?

Research how to write a business proposal to share within your workplace. For example, see:

- [Write a Proposal to Management](https://www.wikihow.com/Write-a-Proposal-to-Management)
- [How to present an idea to your boss](https://www.indeed.com/career-advice/career-development/how-to-present-an-idea-to-your-boss-template)

Imagine taking a risk in a software development job. You want to suggest a new step in your e-commerce checkout process, persuading customers to subscribe to 1-day delivery like Amazon Prime. The step might improve customer loyalty or cause confusion and complaints. It might increase revenues. It might be too complicated to get right.

Write a proposal like an email, proposing the step in the checkout process to your team, what risks you perceive and how you will mitigate the risks. Write it in a document between 0.5 to 1 page long.

### Maximum time in hours

1.5

### How to submit

- Share your document on the cohort channel, asking for feedback.
- Give feedback on your peer's proposal.
- Post a screenshot of your post with some feedback, if possible, as a comment on this issue
- Also post your google doc as a comment here. Make sure the file is open for comments.

Contributor guide

Open the contributing guide

Research direction

Review the linked guidance on writing a proposal to management and presenting an idea to a boss. Draft a 0.5–1 page email proposing a checkout step, including perceived risks and mitigations. Share it on the cohort channel, give peer feedback, and post the document and feedback screenshot here.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Documentation
Difficulty
1/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.