Every project starts with an objective – move all legacy databases into one global NoSQL database, launch a stock trading platform, achieve net-zero carbon emissions by 2030, build a social media app, etc.
Once the initiative is commenced, the first order of business is identifying major chunks of work called epics. Each organization tends to define epics differently. However, epics are generally large bodies of work that can be broken into smaller parts (user stories).
Let’s suppose we’re building a stock trading platform. In such project, some of the epics might be opening an account, transferring funds, buying stocks, selling stocks, manage user settings, and so forth.
It is important to define epics in simple terms without using technical jargons so that they are understood by everyone involved in the project.