0% found this document useful (0 votes)
72 views2 pages

Software Project Management Syllabus

Uploaded by

SRIKANTH KETHA
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
72 views2 pages

Software Project Management Syllabus

Uploaded by

SRIKANTH KETHA
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

R-20 Syllabus for CSE, JNTUK w. e. f.

2020 – 21

JAWAHARLAL NEHRU TECHNOLOGICAL UNIVERSITY KAKINADA


KAKINADA – 533 003, Andhra Pradesh, India

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

L T P C
III Year – I Semester
3 0 0 3
SOFTWARE PROJECT MANAGEMENT
(Professional Elective –I)

Course Objectives:
At the end of the course, the student shall be able to:
• To describe and determine the purpose and importance of project management from the
perspectives of planning, tracking and completion of project
• To compare and differentiate organization structures and project structures
• To implement a project to manage project schedule, expenses and resources with the application of
suitable project management tools

Course outcomes:
Upon the completion of the course students will be able to:-
• Apply the process to be followed in the software development life-cycle models
• Apply the concepts of project management & planning
• Implement the project plans through managing people, communications and change
• Conduct activities necessary to successfully complete and close the Software projects
• Implement communication, modeling, and construction & deployment practices in software
development

UNIT-I:
Conventional Software Management: The waterfall model, conventional software Management
performance.
Evolution of Software Economics: Software Economics, pragmatic software cost estimation.
Improving Software Economics: Reducing Software product size, improving software processes,
improving team effectiveness, improving automation, Achieving required quality, peer inspections.
The old way and the new: The principles of conventional software Engineering, principles of modern
software management, transitioning to an iterative process.

UNIT-II:
Life cycle phases: Engineering and production stages, inception, Elaboration, construction, transition
phases.
Artifacts of the process: The artifact sets, Management artifacts, Engineering artifacts, programmatic
artifacts.

UNIT- III:
Model based software architectures: A Management perspective and technical perspective.
Work Flows of the process: Software process workflows, Iteration workflows.
Checkpoints of the process: Major mile stones, Minor Milestones, Periodic status assessments.
Iterative Process Planning: Work breakdown structures, planning guidelines, cost and schedule
estimating, Iteration planning process, Pragmatic planning.
UNIT- IV:
Project Organizations and Responsibilities: Line-of-Business Organizations, Project Organizations,
evolution of Organizations.
Process Automation: Automation Building blocks, The Project Environment.
Project Control and Process instrumentation: The seven core Metrics, Management indicators, quality
indicators, life cycle expectations, pragmatic Software Metrics, Metrics automation.
R-20 Syllabus for CSE, JNTUK w. e. f. 2020 – 21

JAWAHARLAL NEHRU TECHNOLOGICAL UNIVERSITY KAKINADA


KAKINADA – 533 003, Andhra Pradesh, India

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

UNIT-V:
Agile Methodology, ADAPTing to Scrum, Patterns for Adopting Scrum, Iterating towards Agility.
Fundamentals of DevOps: Architecture, Deployments, Orchestration, Need, Instance of applications,
DevOps delivery pipeline, DevOps eco system. DevOps adoption in projects: Technology aspects, Agiling
capabilities, Tool stack implementation, People aspect, processes

Text Books:
1. Software Project Management, Walker Royce, PEA, 2005.
2. Succeeding with Agile: Software Development Using Scrum, Mike Cohn, Addison Wesley.
3. The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in
Technology Organizations, Gene Kim , John Willis , Patrick Debois , Jez Humb,1st Edition,
O’Reilly publications, 2016.

Reference Books:
1. Software Project Management, Bob Hughes,3/e, Mike Cotterell, TMH
2. Software Project Management, Joel Henry, PEA
3. Software Project Management in practice, Pankaj Jalote, PEA, 2005,
4. Effective Software Project Management, Robert [Link], Wiley,2006
5. Project Management in IT, Kathy Schwalbe, Cengage

Common questions

Powered by AI

Agile methodology contrasts with traditional project management by prioritizing flexibility, customer collaboration, and rapid iteration. While traditional models often follow predetermined plans, Agile embraces change, allowing for continuous delivery and the ability to respond to evolving project complexities. This approach mitigates risks associated with rigid planning and often results in more adaptive and rapid outcomes .

Scrum patterns, such as sprints, stand-ups, and retrospectives, structure team activities for efficiency and focus. Their iterative nature fosters continual reassessment and integration of feedback, streamlining the adaptation of agile practices. This reinforces team collaboration, transparency, and accountability, essential for successfully embedding agile frameworks into software development processes, resulting in improved project outcomes and stakeholder satisfaction .

Software process workflows delineate the sequential steps necessary to develop software, including requirements gathering, design, implementation, testing, and maintenance. By establishing clear workflows, project management can monitor progress, ensure resources are correctly utilized, and align team activities with project goals, thus enhancing overall effectiveness and efficiency in achieving desired outcomes .

Adopting DevOps in software projects enhances delivery speed, quality, and reliability by integrating development and operations teams for continuous collaboration. Core components of DevOps include architecture, deployments, orchestration, and a robust delivery pipeline, focusing on processes, technology, and people. This synergy reduces bottlenecks and accelerates product release cycles, ensuring high-quality outcomes .

Transitioning from conventional to modern software management involves adopting iterative processes instead of linear approaches like the waterfall model. This shift improves adaptability and team effectiveness by facilitating continuous feedback and incremental improvements in projects. It supports better alignment with evolving client needs and technological changes, potentially leading to higher project success rates .

Pragmatic software metrics, such as those related to cycle time, code quality, and defect rates, provide actionable insights into the software development process. These metrics guide project managers in optimizing workflows, allocating resources effectively, and identifying areas for process improvement. Their practical application enables data-driven decision-making and facilitates the achievement of project objectives within time and budget constraints .

Iterative process planning allows for systematic progress through defined phases such as inception, elaboration, construction, and transition. It provides flexibility by incorporating periodic milestones and assessments, enabling adjustments without disrupting the entire project timeline. This leads to better resource allocation, risk management, and quality assurance throughout the project's lifecycle .

Integrating agile principles into existing project management structures often necessitates organizational transformation, including shifts in team dynamics, communication, and project segmentation. While it promotes flexibility and responsiveness to change, challenges may arise in scaling agile practices across larger projects or traditional corporate frameworks. It encourages a shift towards dynamic planning and iterative development, potentially leading to enhanced innovation and project adaptability .

Project control and process instrumentation involve monitoring and managing the seven core metrics: schedule, cost, scope, quality, risk, resources, and customer satisfaction. By using these metrics, project managers can track project health, make informed decisions, and anticipate issues. Metrics automation supports timely data processing, enabling quicker interventions and contributing significantly to project efficiency and success .

Managing projects through a lifecycle perspective involves challenges such as maintaining alignment across phases, ensuring continuity in communication, and adapting to changes without derailing progress. These can be addressed by defining clear milestones, employing standardized management artifacts, and fostering a culture of iterative review and adjustment, thereby enhancing coherence and adaptability across the project lifecycle .

You might also like