Photo by Austin Distel on Unsplash
Introduction to Planning a Startup through User Personas
AWS Project Bootcamp Week 00 : Planning and Requirement Gathering
Table of contents
Introduction
Hey Reader, I am going through the Free AWS Project Bootcamp on freeCodeCamp by hosted by Andrew Brown and this blog contains the learning of my first week what I specially first part regarding the planning and user personas on various level while planning a startup. I am attaching the images from video itself for reference
Resource link - AWS PROJECT BOOTCAMP
Building CURDDER Startup!
So at first an introduction is made by assuming the startup (yeah CURDDER!!). CURDDER is a a Ephemeral first microblogging platform aka community Snapchat with some enhancements. So this startup is founded by Sam and lets assume you as Cloud Engineer which is on contract for 6 months and you will be working with Web Dev Team under his manager Tony and they have a fractional CTO Aaron onboard with them(Fractional CTO basically advices the Firm regarding leadership in tech and it is part time)
Lets see the perspective of each persona
Cloud Engineer Persona : You :)
So lets cheer as its your first day and have a meet with Aaron and he is explaining about the project. As per the trend we are using microservice architecture and ditching the monolithic architecture. Well what does it means lets see. Monolithic is like a all in one code, centralized at single place. On other hand microservices are tends to be separate function or service for each functionality. Here the AWS Lambda Functions play great role. It is serverless function which is used to create the microservice
Next tech stack of our product is React as Frontend and Flask Backend. Leveraging AWS services to build, host, scale and maintain the application. So first task is plan the requirements, services and budget by analyzing an preparing a report on it
CTO’s perspective : Aaron
Now lets see some management side. Basically here the management defines 3 main pillars Functionality, Cost and Time. Quality is something we achieve by balancing all these factors. Mostly if we go for two we lack one of them.
Investors Perspective
Investors they all want return on their investment. In short they want to Startup to manage the infrastructure cost along with marketing cost. In this case they funded Startup with salary of employee up to 6 months for now and after the final report they will decide of future investment
In short Cloud Engineer sees the technical side like building maintaining the project, while CTO foresees technical requirements and future state of project. Overall we need to manage time cost and efforts and for you as cloud engineer here learn iterate and show back!
In this part the planning and requirement gathering phase is discussed which is most crucial and initial step of any startup or project. Next there is architecture planning phase in which design the outline using various standards.