Grow in your IT career - Best practices of working in IT Projects!
Tausief Shaikh ??
Head of Technology | Project management, HighPerformance, Design & Architecture, Leadership
Hello LinkedIn Success Family, Today's topic would be very useful in your IT Career Growth. We would dig deep into, 'How IT projects work?' & 'What are the Best practices of working in IT'. Today we would cover Part1, and 2nd part would be published tomorrow.
You would need to understand that IT is a very matured industry, and working with processes, people, systems, needs you to be get organized and make right actions at the right time.
Here is standard steps of project development:
Based on whatever is your role (in team), you would need to master those phases. I would highly request you to spend time in each of these phases, and master it & try to contribute to project to the best of your abilities.
Agile approach of software development
Since past many years, not majority of industry is using Agile approach of software development. It simply says, develop & deliver project in small phases. Each phase can have 1-4 weeks of working cycle called Sprints.
Below is overview of what & how working in Agile looks like:
In simple words, if business had 10 functionalities to be developed, then team decides how much is possible to do in 2weeks. And accordingly develops and delivers it. All meetings that you see above, are in place, to make above possible.
领英推è
Must know Checlist for project success
Regarding of what project you take, the basic flow of working would be the same. So if you master it once, you would be able to stay peaceful throughout your IT career. Yes, it would be dynamic, & few thigns may vary from project-to-project, but if you have base understanding, then you can adapt easily.
Grooming Checklist
- Did you read the ticket?
- Understood the requirement (At least 70-80% clear)
- Come up with list of questions Functional
- Think high-level Approach
- Put high-level block diagram(services/components)
- Come up with list of questions Technical
- Identify Dependencies (Devops, 3rd party, Architect, Any)
- Impact analysis - to existing system.
- Suggestions back to Product Owner
- Time Estimate
- Story point estimate
High-Level Design Checklist:
- Identify the overall system architecture and its components
- Consider scalability and performance requirements
- Evaluate the feasibility of the design
- Define the requirements and functionalities of the system
- Identify the constraints and limitations of the system
- Evaluate potential risks and determine how to mitigate them
- Identify security and privacy considerations
- Consider the impact of the design on users and stakeholders
- Create a plan for testing and evaluating the system
I would request you to understand each of the point & start learning and growing in it. And keep constantly applying in your project. The more you implement practically, the better you would become.
Wish you great Career Success. Happy to share!
?? If you want to build a successful career and life then join us in CareerTransformation(CT). Here we implement techniques for high performance, work-life success & massive career success.
? Next batch starts from 1May, 9PM (Register Now for your growth):
Have a great day!