The 80 / 20 rule for software developers

Pareto's principle visualized

What can we do about it?

A case study

Troosh’s project page
  1. Mentor can link resources to this project. Teams can later see these resources collectively on the project page.
  2. Dynamically adding users to teams.
  3. Real-time notifications for task completion for both users and mentors.
  4. Optional prerequisites for users to know before joining this project.
  5. Ability to chat privately with your team or with your mentor.
  6. Feedback provided by the mentor for each task completion.
  7. Awards given per task or project completion. This gives teams a sense of reward along with what they learnt through the process. They can later show off these awards to their friends!

Conclusion

--

--

--

Developer for a living. Developing on my spare time. Pretty much just developing at this point.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Code is a Liability

CS 373 Fall 2020: Entry 4

Getting Started with Business Process Automation (BPA) in Document Management in 2020

Business Process Automation (BPA) in Document Management

Creating a Hyperledger Composer Application on Windows 10 Home

My Experience Working For The Royal Canadian Air Force As An iOS Developer

Storybook’s greatest strength (and weakness)

Quick guide to Android localization with Localazy

The Twelve-Factor App Methodology Explained #1

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Dimitris Stefanakis

Dimitris Stefanakis

Developer for a living. Developing on my spare time. Pretty much just developing at this point.

More from Medium

Should you Learn to Use No-Code Tools?

Best Business Process Management Software Solution-bpmEdge BPMS

Row headers for your iOS Gantt charts

Low Code, No Code.