Software Engineers Process
I'm gonna talk about how to develop your own process that works for you and your teammates.
If you are a fresher or an undergraduate and you don't know how to start your career as a programmer within a company or as a freelancer then this is definitely the right place you have come to.
I started my career as a JavaScript programmer and had my way of doing coding. Little did I know my way was flawed and could not match up to my senior's expectations. Back then agile was raw and books weren't there on the subject.
If you have a process of doing all the activities for software development like analysis, design coding and testing then this article is not for you and you can close it. Rock on.
But just if in case you need a systematic way of development just as mentioned in software engineering books then continue reading.
We need to do the software process activities like requirements gathering, analysis, design, coding and testing.
You could be assigned to analysis, design, coding and testing tasks to whatever role you are comfortable with.
We need agile approaches like scrum, xp, or any other approach to start with a product backlog. We then need to make a project plan with estimates for each of the use cases.
Start with use cases that are prioritized and follow each of the activities and build your confidence as you work through them.
You don't have to be an expert in everything. Just start small and be greater than each sprint. Sprint is a cycle for development work and it could be from 2 weeks or a month.
We need to do daily stand up where each of the teammates discuss what is being developed by them and we don't need to know the details. Just know who is developing which use case.
Don't worry in the initial stages of development. Just keep a Positive attitude and believe that you can be part of development team and that you will succeed and get the habit of the hardcore development work.
If in case you don't have the right results then pair up with an expert programmer and he will guide you with how the process works.
You could later on then be an expert one day and pair up with another junior some day.
You don't have to read books for each of the framework activities. Just work with a team and follow the practices followed by the team. Wait I said practices, yes the practices and principles mentioned in the software engineering book by Roger Pressman is the definite guide for you to proceed with what's right and what's wrong.
For example. Principle - The Reason it all exists. Which means What is the purpose of this app being developed.
Just go through the principles and practices mentioned in the SE Book and put them to use practically. Just try to use your intuition with the practices. You will become an expert by the end of the project which could mean that you will have development experience between 6 months to 1 year.
And finally try to get more experience by working simultaneously on other freelance projects and follow the same set of principles with every project.
There is more, if still you aren't clear with how the agile development works then buy agile development books and just read the parts whee you are lacking skills. You don't have to read each chapter of agile books, just read about what you're lacking.
Finally take feedback from the team about what was right or wrong and Share feedback with other teammates as well.
And that should be all. You will become an experienced programmer in software engineering.
Remember you are building a systematic process that helps you be a great Software Engineer.