Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

The Art of Software Project Management For IT Engineers

The Important Components of Software Planning. learn all these in an exclusive handout by Tetranoodle Technologies.
Access the full course here - https://bit.ly/2G7fa4V

About-
Website: https://courses.tetranoodle.com/
Facebook: https://www.facebook.com/tetranoodletech
Twitter: https://twitter.com/TETRANOODLE
Linkedin: https://www.linkedin.com/company/tetranoodle/
YouTube: https://www.youtube.com/channel/UCAiIK20nDamhq70NMnLG8wA
Instagram: https://www.instagram.com/tetranoodle/
Udemy: https://www.udemy.com/user/manujaggarwal

  • Be the first to comment

  • Be the first to like this

The Art of Software Project Management For IT Engineers

  1. 1. The Art of Software Project Management - Initiation @tetranoodleWhat is Software Project Management is all about? WHAT IS A SOFTWARE PROJECT CHARTER? Software Project Charter is a set of activities that a Software Project Manager performs to make sure everyone related to the Project is in the same page with respect to requirements and responsibilities. Project Scope Project Charter Sign off Project Objective Project Constraints Project Assumptions Project Risks Stake HoldersProject Manager
  2. 2. The Art of Software Project Management - Initiation @tetranoodleWhat is Software Project Management is all about? SOFTWARE PROJECT MANAGEMENT – TRIPLE CONSTRAINTS Triple Constraints are the Project Constraints that the Project Manager has to work with in a Software Project. In the Traditional approach, Requirements used to be a Fixed component and Cost a variable component. Traditional Approach Requirements Time Quality Cost FIXED VARIABLE
  3. 3. The Art of Software Project Management - Initiation @tetranoodleWhat is Software Project Management is all about? In the Agile approach the time is a Fixed component and Requirements is a variable component. Agile Approach SOFTWARE PROJECT MANAGEMENT – TRIPLE CONSTRAINTS Requirements Cost Quality Time VARIABLE FIXED
  4. 4. The Art of Software Project Management - Planning @tetranoodleWhat is Software Project Management is all about? WHAT ARE THE IMPORTANT COMPONENTS OF SOFTWARE PLANNING? Important component of a Software Project Planning Is the estimations and there are major estimations that are essential, Effort, Schedule and Cost. For a Successful Project, 3 estimations are critical Effort Estimation Schedule Estimation Cost Estimation
  5. 5. The Art of Software Project Management - Planning @tetranoodleWhat is Software Project Management is all about? ! Critical Path is the list of activities in the schedule that take the longest duration ! The more the number of activities in the Critical Path, the more will be the probability of the Project extending beyond the schedules Software Project Management – Critical Path Critical Path as the name implies plays a significant role in Project Planning. This has to be taken appropriate care and control for a successful execution of any Project. ! Slack or float is the amount of time an activity may be delayed from its early start without delaying the project finish date. ! The more the number of Critical Paths in a Project higher will be the risk of them extending beyond the schedules. Critical Path
  6. 6. The Art of Software Project Management - Team @tetranoodleWhat is Software Project Management is all about? WHY DOES SOFTWARE PROJECT MANAGER NEED TO MANAGE THE TEAM? Team is a very important component in the Software Project and keeping the team motivated is essential. How do you motivate the team? 3 Facilitate and felicitate Achievements of the team 1 Generate a feeling to act and contribute 2 Activate the team to work towards the Goal
  7. 7. The Art of Software Project Management - Team @tetranoodleWhat is Software Project Management is all about? SUCCESSFUL TEAMS Successful Teams will have these six powerful factors. Successful Team Physiological SafetySelf Sustaining Belonging Self Realization Esteem
  8. 8. The Art of Software Project Management – Quality Assurance @tetranoodleWhat is Software Project Management is all about? Why is Quality Assurance (Testing) is needed? Testing takes care of making sure that Software works as designed and all the requirements function as expected. Conformance to requirements Testing can only capture specification misses Testing does not make software perfect Product Quality depends on the amount of testing There is no definitive end to Testing Testing is not an alternative to Reviews Software Testing
  9. 9. The Art of Software Project Management – Quality Assurance @tetranoodleWhat is Software Project Management is all about? What are the types of Testing? Unit Testing, Integration Testing, Regression Testing and Smoke Testing are the four major types of Testing. Integration Testing Integration Testing is done after all the individual modules of the software is developed and to test the linkages and dependencies of each functionality with the other. Regression Testing Regression Testing is done to make sure the new functionality introduced does not break the existing working functionality of the software. Unit Testing Unit Testing is the first level of testing to check the functionality of the software and is normally executed by the developers. Smoke Testing This is a representative testing to ensure a build is ready to be deployed to the next stage of the software development 1 2 3 4
  10. 10. The Art of Software Project Management – Closure @tetranoodleWhat is Software Project Management is all about? HOW DO WE COMPLETE A SOFTWARE PROJECT? Software Project Manager must ensure to complete the release of all the resources before the Project is formally completed. Com plete Deliverables Release Resources Project Archival Project Post-m ortem Project Closure
  11. 11. The Art of Software Project Management – Closure @tetranoodleWhat is Software Project Management is all about? Why is a Project Post mortem necessary? Post mortem is needed to ensure all the Project learnings are appropriately documented for future Projects. Identify and document what went well and what did not First Second Third Fourth Retain knowledge for the future assignments Provide feedback to the Team members for their contribution Last but not the least, identify the improvement areas for self and work on them.

×