SlideShare a Scribd company logo
Software Project
Requirements with Project
Team Member Requirement
A MODEL FOR ALIGNING
KAUSHAL MISHRA (MCA )
SRMGPC ,LUCKNOW
Introduction
What are the root causes that lead some project teams to operate well, while others struggle?
Underperforming project teams may result from a weak change management plan, lack of talent on the project team, or
insufficient stakeholder support, among other factors.
 Many IT projects today have a project charter. Key components of a charter include the project scope, timeline, budget,
approach and expected benefits.
 All individuals related to the project want the best for the organization. However, when they see the project charter
through their own prism, they may see the scope, the benefits and the approach quite differently. This is why it is critical
to align early and often.
What does a high-performance project team look like?
Project Roles and Responsibilities
Projects of different sizes have different needs for how the people are organized. In a small project, little organization
structure is needed. There might be a primary sponsor, project manager and a project team.
 Analyst : The Analyst is responsible for ensuring that the requirements of the business clients are captured and
documented correctly before a solution is developed and implemented.
 Change Control Board :The Change Control Board is usually made up of a group of decision makers authorized to
accept changes to the projects requirements, budget, and timelines
 Client: This is the people (or groups) that are the direct beneficiaries of a project or service. They are the people for
whom the project is being undertaken.
 Client Project Manager : If the project is large enough, the business client may have a primary contact that is
designated as a comparable project manager for work on the client side.
Project Roles and Responsibilities
 Database Administrator: A Database Administrator is a specialist that models, designs and creates the databases and
tables used by a software solution
 Designer: The designer is responsible for understanding the business requirements and designing a solution that will
meet the software needs.
 Developer: The Developer is responsible for the actual building of the solution.
 Project Manager: This is the person with authority to manage a project. This includes leading the planning and the
development of all project deliverables. The project manager is responsible for managing the budget and schedule and
all project management procedures (scope management, issues management, risk management, etc.)
 Quality Manager : On a large project, quality management could take up a large amount of project management time.
 Sponsor : This is the person who has ultimate authority over the project. The Sponsor provides project funding,
resolves issues and scope changes, approves major deliverables and provides high-level direction.
 Stakeholder : These are the specific people or groups who have a stake, or an interest, in the outcome of the project.
 Suppliers / Vendors , Tester , Users
Project Roles and Responsibilities
Project Team : The project team consists of the full-time and part-time resources assigned to work on the deliverables of
the project. This includes the analysts, designers, programmers, etc. They are responsible for:
 Understanding the work to be completed.
 Planning the assigned activities in more detail if needed.
 Completing assigned work within the budget, timeline and quality expectations.
 Informing the project manager of issues, scope changes, risk and quality concerns.
 Proactively communicating status and managing expectations.
How to Put together a high performance Team
Project Team Requirment
In most cases, an organization’s most valuable asset is its people. The same is true for project teams. Project
success generally depends on individual talent, as well as team performance. Highly engaged and motivated
teams are often more likely to perform at a high level and achieve their objectives.
 Team members know each other well and understand everyone's strengths and weaknesses.
 They genuinely respect and care about each other.
 They believe in the organization’s mission and the projects objectives.
 They celebrate successes and learn from failures.
Provide High-Quality Leadership
 Establish your team’s objectives and purpose – It’s important to verify that all team members know exactly what target
they are aiming for and why it’s important to both the organization and the team. People may be more likely to work
toward a common goal when they clearly understand its meaning and their contribution.
 Establish a few rules – You can help build trust when you communicate what’s expected. It’s also generally a good idea
to plan ahead in order to manage potential conflicts in a positive way.
 Demonstrate trust – Allow people to take risks, experience failures and learn from their mistakes. Encourage creativity .
You shouldn’t expect team members to put trust in you if you can’t first demonstrate that you trust them.
 Require accountability – Regularly assess both team and individual performance. Deal with issues immediately by
enforcing the established rules. Be sure to offer criticism constructively and privately. Without accountability, rules may
be ignored, projects derailed and leaders may not respected.
 Demonstrate your leadership – Model the work ethic, honesty, and level of communication and cooperation you expect.
Show team members what success looks like, and they may be inspired to follow you.
Recognize and Reward
 People often like to be appreciated for a job well done. As a project leader, it's important to recognize team members
when they meet important deadlines or achieve significant milestones. Praise from a leader can make team members
feel appreciated, and may inspire the entire team to keep working toward the goal. However, keep in mind that not
everyone may share the same enthusiasm for the spotlight. When you truly know your team well, you'll learn their
preferences.
Handle Delays Professionally
 Work interruptions, technical troubles, additional responsibilities and unforeseen circumstances can delay a
project. While they may be normal and expected in business, it doesn’t make missing a deadline any easier to
swallow. Leadership is often judged by how people handle obstacles and delays, so make sure to do it
professionally.
 Start by evaluating the severity of the problem and remember that not every delay is a catastrophe. Next, assess
how the delay may affect other aspects of the project, and what resources are available to shift to the problem.
Finally, engage team members on finding and implementing the most effective solution. Also, make sure to keep
appropriate stakeholders informed of the delay while providing an appropriate solution.
 High-performing project teams can help make a project manager’s life easier. Start building your team by
following these tips for improving project team performance. They're easy to implement and can pay off in a
“dream team” that may help make projects more successful.
Software Project Requirement
The software requirements are description of features and functionalities of the target system. Requirements convey
the expectations of users from the software product
Requirement Engineering
 The process to gather the software requirements from client, analyze and document them is known as
requirement engineering.
 The goal of requirement engineering is to develop and maintain sophisticated and descriptive ‘System
Requirements Specification’ document.
Requirement Engineering Process
It is a four step process, which includes –
 Feasibility Study
 Requirement Gathering
 Software Requirement Specification
 Software Requirement Validation
Let us see the process briefly -
Feasibility study
This feasibility study is focused towards goal of the organization. This study analyzes whether the software product
can be practically materialized in terms of implementation, contribution of project to organization, cost constraints
and as per values and objectives of the organization. It explores technical aspects of the project and product such as
usability, maintainability, productivity and integration ability.
 The output of this phase should be a feasibility study report that should contain adequate comments and
recommendations for management about whether or not the project should be undertaken.
Requirement Gathering and SRS
If the feasibility report is positive towards undertaking the project, next phase starts with gathering requirements from the
user. Analysts and engineers communicate with the client and end-users to know their ideas on what the software should
provide and which features they want the software to include.
Software Requirement Specification
SRS is a document created by system analyst after the requirements are collected from various stakeholders.SRS defines how
the intended software will interact with hardware, external interfaces, speed of operation, response time of system,
portability of software across various platforms, maintainability, speed of recovery after crashing, Security, Quality,
Limitations etc.
Software Requirement Specification
Requirements can be checked against following conditions -
 If they can be practically implemented
 If they are valid and as per functionality and domain of software
 If there are any ambiguities
 If they are complete
Requirement elicitation process
 Requirements gathering - The developers discuss with the client and end users and know their expectations from the
software.
 Organizing Requirements - The developers prioritize and arrange the requirements in order of importance, urgency
and convenience.
 Negotiation & discussion - If requirements are ambiguous or there are some conflicts in requirements of various
stakeholders, if they are, it is then negotiated and discussed with stakeholders. Requirements may then be prioritized
and reasonably compromised . The requirements come from various stakeholders. To remove the ambiguity and
conflicts, they are discussed for clarity and correctness. Unrealistic requirements are compromised reasonably.
 Documentation - All formal & informal, functional and non-functional requirements are documented and made
available for next phase processing.
 Requirements Elicitation is the process to find out the requirements for an intended software system by
communicating with client, end users, system users and others who have a stake in the software system development.
Requirement Elicitation Techniques
 There are various ways to discover requirements
Interviews:
Structured (closed) interviews, where every single information to gather is decided in advance, they follow pattern and
matter of discussion firmly (confidently).
Non-structured (open) interviews, where information to gather is not decided in advance, more flexible and less biased.
Oral interviews
Written interviews
One-to-one interviews which are held between two persons across the table.
Surveys
 Organization may conduct surveys among various stakeholders by querying about their expectation and requirements
from the upcoming system.
Requirement Elicitation Techniques
Questionnaires:
 A document with pre-defined set of objective questions and respective options is handed over to all stakeholders to
answer, which are collected and compiled
Brainstorming:
 An informal debate is held among various stakeholders and all their inputs are recorded for further requirements
analysis.
Observation:
 Team of experts visit the client’s organization or workplace. They observe the actual working of the existing installed
systems. They observe the workflow at client’s end and how execution problems are dealt. The team itself draws some
conclusions which aid to form requirements expected from the software.
Aligning Modal
Typically, alignment is required on three levels:
 Sponsors and stakeholders—around the future state vision.
 Management—around a plan that can be executed.
 Project team—around priorities and tasks at hand.
Sponsor and Stakeholder Alignment
 Most executives feel that they see things the same way, especially when it comes to decisions that they made
together. It is true that most projects are budgeted and start with consent from all appropriate executives. But
does consent mean alignment? In reality, it’s likely that each executive wound up (tension) with their own
unique vision of what will occur after the project is complete, and what it will take to successfully execute the
project.
 It is hard to convince executives to meet repeatedly to understand the changes that can push a project off
target and to align their resources to the project goals. But this is the only way to stay on track and avoid
wasting time on the rework that must will be required if team members take the project towards the
misaligned future state visions in their department leads’ heads.
Management Alignment
 Middle management is cynical(selfish). They have seen these projects come and go. In fact, they say, we have more
projects than we can keep track of right now. Yet, without a firm belief from middle management that a given project
can and will be completed, you can count only on one thing—apathy( Nutral).
 It may be tedious(Boring), but it’s well worth the effort to gather all relevant data that could impact the project’s
success early on. This includes concerns, dependencies, vacations and other availability information. Chances are, some
of that information is relevant to the project, some of it is good to know, and some of it is just fear of change. In all
three cases, you want to hear it out and account for it .
 Once the project plan has been adjusted to account for relevant data, people start believing that this is a real plan and
you are not just going through the motions. After all, they have no more excuses to keep it from happening.
Project Team Alignment
 Most project teams consist of a core team (full-time participants) and an extended team (part-time participants).
All of the members of the extended team and many of the core team members likely have other responsibilities
in the organization, perhaps participating on other project teams. Not only are team members often distracted,
but they each also have their own opinions about how the project should be conducted. It is very hard for a team
to work in a coordinated fashion when each member has their own idea of how a given activity should be
executed and their role in it.
 There are many ways to align a project team around the approach: training the team in the methodology that is
being used, team-building exercises, offsite workshops, communication programs, etc. All of these take time and
effort, but they are well worth it.
**********
References
1. Abraic.in (Mikhail Papovsky @mpapov)
Founder and CEO of Abraic, Inc. Dedicated to improving the outcomes of IT
investments.
2. http://www.lifecyclestep.com/open/408.0LifecycleRoles.html
(408.0 Project Roles and Responsibilities)
3. Reference paper : Robert Hans Tshwane University of Technology, Pretoria,
South Africa hansr@tut.ac.za
Presented By – KAUSHAL MISHRA

More Related Content

What's hot

4 p’s of management spectrum and the w5hh principle
4 p’s of management spectrum and the w5hh principle4 p’s of management spectrum and the w5hh principle
4 p’s of management spectrum and the w5hh principle
Mohammad Hafiz-Al-Masud
 
Jimmy_CV
Jimmy_CVJimmy_CV
Software Project Management Lab Manual Lab 1
Software Project Management Lab  Manual  Lab 1Software Project Management Lab  Manual  Lab 1
Software Project Management Lab Manual Lab 1
sundas Shabbir
 
Hr Management
Hr ManagementHr Management
Hr Management
asim78
 
Project Stakeholder Management - PMBOK 5
Project Stakeholder Management - PMBOK 5Project Stakeholder Management - PMBOK 5
Project Stakeholder Management - PMBOK 5
pankajsh10
 
Project Management case analysis
Project Management case analysisProject Management case analysis
Project Management case analysis
Wakas Khalid
 
Project Management 101 Primer
Project Management 101   PrimerProject Management 101   Primer
Project Management 101 Primer
Gary Drumm
 
Project Management Principles
Project Management PrinciplesProject Management Principles
Project Management Principles
Anand Subramaniam
 
6. project human resource management
6. project human resource management6. project human resource management
6. project human resource management
Mohamed Salah Eldien Mohamed Ali
 
UCISA Major Project Governance Assessment Toolkit
UCISA Major Project Governance Assessment ToolkitUCISA Major Project Governance Assessment Toolkit
UCISA Major Project Governance Assessment Toolkit
Mark Ritchie
 
Presentation by mangesh sardesai
Presentation by mangesh sardesaiPresentation by mangesh sardesai
Presentation by mangesh sardesai
PMI_IREP_TP
 
Agile: JAD Requirements Elicitation
Agile:  JAD Requirements ElicitationAgile:  JAD Requirements Elicitation
Agile: JAD Requirements Elicitation
Ernadel Sioson
 
ch 22. Project management in SE
ch 22. Project management in SEch 22. Project management in SE
ch 22. Project management in SE
esam123
 
Project Management 101
Project Management 101Project Management 101
Project Management 101
MurftheSurf
 
Project management competencies
Project management competenciesProject management competencies
Project management competencies
angelicabeato
 
Why Do So Many Software Projects Fail?
Why Do So Many Software Projects Fail?Why Do So Many Software Projects Fail?
Why Do So Many Software Projects Fail?
Phil Comelio
 
Identifying a project in trouble and re-planning
Identifying a project in trouble and re-planningIdentifying a project in trouble and re-planning
Identifying a project in trouble and re-planning
mfarbstein
 
Promoting knowledge sharing in projects
Promoting knowledge sharing in projectsPromoting knowledge sharing in projects
Promoting knowledge sharing in projects
Louise Worsley
 
Post mortem report
Post mortem reportPost mortem report
Post mortem report
Kuaci Pedas
 
Introduction to Project Management (workshop) - v.2
Introduction to Project Management (workshop) - v.2Introduction to Project Management (workshop) - v.2
Introduction to Project Management (workshop) - v.2
Mena M. Eissa
 

What's hot (20)

4 p’s of management spectrum and the w5hh principle
4 p’s of management spectrum and the w5hh principle4 p’s of management spectrum and the w5hh principle
4 p’s of management spectrum and the w5hh principle
 
Jimmy_CV
Jimmy_CVJimmy_CV
Jimmy_CV
 
Software Project Management Lab Manual Lab 1
Software Project Management Lab  Manual  Lab 1Software Project Management Lab  Manual  Lab 1
Software Project Management Lab Manual Lab 1
 
Hr Management
Hr ManagementHr Management
Hr Management
 
Project Stakeholder Management - PMBOK 5
Project Stakeholder Management - PMBOK 5Project Stakeholder Management - PMBOK 5
Project Stakeholder Management - PMBOK 5
 
Project Management case analysis
Project Management case analysisProject Management case analysis
Project Management case analysis
 
Project Management 101 Primer
Project Management 101   PrimerProject Management 101   Primer
Project Management 101 Primer
 
Project Management Principles
Project Management PrinciplesProject Management Principles
Project Management Principles
 
6. project human resource management
6. project human resource management6. project human resource management
6. project human resource management
 
UCISA Major Project Governance Assessment Toolkit
UCISA Major Project Governance Assessment ToolkitUCISA Major Project Governance Assessment Toolkit
UCISA Major Project Governance Assessment Toolkit
 
Presentation by mangesh sardesai
Presentation by mangesh sardesaiPresentation by mangesh sardesai
Presentation by mangesh sardesai
 
Agile: JAD Requirements Elicitation
Agile:  JAD Requirements ElicitationAgile:  JAD Requirements Elicitation
Agile: JAD Requirements Elicitation
 
ch 22. Project management in SE
ch 22. Project management in SEch 22. Project management in SE
ch 22. Project management in SE
 
Project Management 101
Project Management 101Project Management 101
Project Management 101
 
Project management competencies
Project management competenciesProject management competencies
Project management competencies
 
Why Do So Many Software Projects Fail?
Why Do So Many Software Projects Fail?Why Do So Many Software Projects Fail?
Why Do So Many Software Projects Fail?
 
Identifying a project in trouble and re-planning
Identifying a project in trouble and re-planningIdentifying a project in trouble and re-planning
Identifying a project in trouble and re-planning
 
Promoting knowledge sharing in projects
Promoting knowledge sharing in projectsPromoting knowledge sharing in projects
Promoting knowledge sharing in projects
 
Post mortem report
Post mortem reportPost mortem report
Post mortem report
 
Introduction to Project Management (workshop) - v.2
Introduction to Project Management (workshop) - v.2Introduction to Project Management (workshop) - v.2
Introduction to Project Management (workshop) - v.2
 

Similar to Software Project Requirement and Team Requirement Model

SDLC & Project Team roles_in practice
SDLC & Project Team roles_in practiceSDLC & Project Team roles_in practice
SDLC & Project Team roles_in practice
bizpresenter
 
Role andresponsiblities in project management
Role andresponsiblities in project managementRole andresponsiblities in project management
Role andresponsiblities in project management
im8home85
 
Part 02 Connecting Business Strategy and Project Management
Part 02 Connecting Business Strategy and Project ManagementPart 02 Connecting Business Strategy and Project Management
Part 02 Connecting Business Strategy and Project Management
Lilis Rusliyawati
 
Project Management Complete Concept
Project Management Complete Concept Project Management Complete Concept
Project Management Complete Concept
MuhammadTalha436
 
An Introduction to Project management(project management tutorials)
An Introduction to Project management(project management tutorials)An Introduction to Project management(project management tutorials)
An Introduction to Project management(project management tutorials)
Daroko blog(www.professionalbloggertricks.com)
 
Software engineering project management
Software engineering project managementSoftware engineering project management
Software engineering project management
jhudyne
 
Project Management
Project ManagementProject Management
Project Management
David Edgerton, Jr.
 
Top Project Management Best Practices.pdf
Top Project Management Best Practices.pdfTop Project Management Best Practices.pdf
Top Project Management Best Practices.pdf
Orangescrum
 
Aula 1 - Project Management Concepts by Roger Pressman
Aula 1 - Project Management Concepts by Roger PressmanAula 1 - Project Management Concepts by Roger Pressman
Aula 1 - Project Management Concepts by Roger Pressman
Rogerio P C do Nascimento
 
Project management assignment help
Project management assignment helpProject management assignment help
Project management assignment help
assignmenthelpp
 
(Fall2016)Lecture2.pptx
(Fall2016)Lecture2.pptx(Fall2016)Lecture2.pptx
(Fall2016)Lecture2.pptx
garkapifye
 
Managing Business Analysis for Agile Development
Managing Business Analysis for Agile DevelopmentManaging Business Analysis for Agile Development
Managing Business Analysis for Agile Development
IJMER
 
Project planning , Productivity metrics,Cost estimation - COCOMO & COCOMO II,...
Project planning , Productivity metrics,Cost estimation - COCOMO & COCOMO II,...Project planning , Productivity metrics,Cost estimation - COCOMO & COCOMO II,...
Project planning , Productivity metrics,Cost estimation - COCOMO & COCOMO II,...
nimmik4u
 
Pmbok
PmbokPmbok
Pmbok
ahsan riaz
 
Project management assignment help
Project management assignment helpProject management assignment help
Project management assignment help
Online Assignment Help
 
Project management concepts
Project management conceptsProject management concepts
Project management concepts
NayyabMirTahir
 
A Guide to Software Development Manager Responsibilities.pdf
A Guide to Software Development Manager Responsibilities.pdfA Guide to Software Development Manager Responsibilities.pdf
A Guide to Software Development Manager Responsibilities.pdf
Laura Miller
 
Unit 1 spm
Unit 1  spmUnit 1  spm
Unit 1 spm
GomathiPrakasham
 
Unit 1 spm
Unit 1  spmUnit 1  spm
Unit 1 spm
GomathiPrakasham
 
Project management 02112009
Project management 02112009Project management 02112009
Project management 02112009
Manish Chaurasia
 

Similar to Software Project Requirement and Team Requirement Model (20)

SDLC & Project Team roles_in practice
SDLC & Project Team roles_in practiceSDLC & Project Team roles_in practice
SDLC & Project Team roles_in practice
 
Role andresponsiblities in project management
Role andresponsiblities in project managementRole andresponsiblities in project management
Role andresponsiblities in project management
 
Part 02 Connecting Business Strategy and Project Management
Part 02 Connecting Business Strategy and Project ManagementPart 02 Connecting Business Strategy and Project Management
Part 02 Connecting Business Strategy and Project Management
 
Project Management Complete Concept
Project Management Complete Concept Project Management Complete Concept
Project Management Complete Concept
 
An Introduction to Project management(project management tutorials)
An Introduction to Project management(project management tutorials)An Introduction to Project management(project management tutorials)
An Introduction to Project management(project management tutorials)
 
Software engineering project management
Software engineering project managementSoftware engineering project management
Software engineering project management
 
Project Management
Project ManagementProject Management
Project Management
 
Top Project Management Best Practices.pdf
Top Project Management Best Practices.pdfTop Project Management Best Practices.pdf
Top Project Management Best Practices.pdf
 
Aula 1 - Project Management Concepts by Roger Pressman
Aula 1 - Project Management Concepts by Roger PressmanAula 1 - Project Management Concepts by Roger Pressman
Aula 1 - Project Management Concepts by Roger Pressman
 
Project management assignment help
Project management assignment helpProject management assignment help
Project management assignment help
 
(Fall2016)Lecture2.pptx
(Fall2016)Lecture2.pptx(Fall2016)Lecture2.pptx
(Fall2016)Lecture2.pptx
 
Managing Business Analysis for Agile Development
Managing Business Analysis for Agile DevelopmentManaging Business Analysis for Agile Development
Managing Business Analysis for Agile Development
 
Project planning , Productivity metrics,Cost estimation - COCOMO & COCOMO II,...
Project planning , Productivity metrics,Cost estimation - COCOMO & COCOMO II,...Project planning , Productivity metrics,Cost estimation - COCOMO & COCOMO II,...
Project planning , Productivity metrics,Cost estimation - COCOMO & COCOMO II,...
 
Pmbok
PmbokPmbok
Pmbok
 
Project management assignment help
Project management assignment helpProject management assignment help
Project management assignment help
 
Project management concepts
Project management conceptsProject management concepts
Project management concepts
 
A Guide to Software Development Manager Responsibilities.pdf
A Guide to Software Development Manager Responsibilities.pdfA Guide to Software Development Manager Responsibilities.pdf
A Guide to Software Development Manager Responsibilities.pdf
 
Unit 1 spm
Unit 1  spmUnit 1  spm
Unit 1 spm
 
Unit 1 spm
Unit 1  spmUnit 1  spm
Unit 1 spm
 
Project management 02112009
Project management 02112009Project management 02112009
Project management 02112009
 

Recently uploaded

Measures in SQL (SIGMOD 2024, Santiago, Chile)
Measures in SQL (SIGMOD 2024, Santiago, Chile)Measures in SQL (SIGMOD 2024, Santiago, Chile)
Measures in SQL (SIGMOD 2024, Santiago, Chile)
Julian Hyde
 
OpenMetadata Community Meeting - 5th June 2024
OpenMetadata Community Meeting - 5th June 2024OpenMetadata Community Meeting - 5th June 2024
OpenMetadata Community Meeting - 5th June 2024
OpenMetadata
 
Unveiling the Advantages of Agile Software Development.pdf
Unveiling the Advantages of Agile Software Development.pdfUnveiling the Advantages of Agile Software Development.pdf
Unveiling the Advantages of Agile Software Development.pdf
brainerhub1
 
LORRAINE ANDREI_LEQUIGAN_HOW TO USE WHATSAPP.pptx
LORRAINE ANDREI_LEQUIGAN_HOW TO USE WHATSAPP.pptxLORRAINE ANDREI_LEQUIGAN_HOW TO USE WHATSAPP.pptx
LORRAINE ANDREI_LEQUIGAN_HOW TO USE WHATSAPP.pptx
lorraineandreiamcidl
 
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian CompaniesE-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
Quickdice ERP
 
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
ALGIT - Assembly Line for Green IT - Numbers, Data, FactsALGIT - Assembly Line for Green IT - Numbers, Data, Facts
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
Green Software Development
 
Transform Your Communication with Cloud-Based IVR Solutions
Transform Your Communication with Cloud-Based IVR SolutionsTransform Your Communication with Cloud-Based IVR Solutions
Transform Your Communication with Cloud-Based IVR Solutions
TheSMSPoint
 
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Neo4j - Product Vision and Knowledge Graphs - GraphSummit ParisNeo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Neo4j
 
Hand Rolled Applicative User Validation Code Kata
Hand Rolled Applicative User ValidationCode KataHand Rolled Applicative User ValidationCode Kata
Hand Rolled Applicative User Validation Code Kata
Philip Schwarz
 
Artificia Intellicence and XPath Extension Functions
Artificia Intellicence and XPath Extension FunctionsArtificia Intellicence and XPath Extension Functions
Artificia Intellicence and XPath Extension Functions
Octavian Nadolu
 
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI AppAI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
Google
 
Energy consumption of Database Management - Florina Jonuzi
Energy consumption of Database Management - Florina JonuziEnergy consumption of Database Management - Florina Jonuzi
Energy consumption of Database Management - Florina Jonuzi
Green Software Development
 
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Atelier - Innover avec l’IA Générative et les graphes de connaissancesAtelier - Innover avec l’IA Générative et les graphes de connaissances
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Neo4j
 
Why Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise Edition
Why Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise EditionWhy Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise Edition
Why Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise Edition
Envertis Software Solutions
 
What is Master Data Management by PiLog Group
What is Master Data Management by PiLog GroupWhat is Master Data Management by PiLog Group
What is Master Data Management by PiLog Group
aymanquadri279
 
KuberTENes Birthday Bash Guadalajara - Introducción a Argo CD
KuberTENes Birthday Bash Guadalajara - Introducción a Argo CDKuberTENes Birthday Bash Guadalajara - Introducción a Argo CD
KuberTENes Birthday Bash Guadalajara - Introducción a Argo CD
rodomar2
 
Empowering Growth with Best Software Development Company in Noida - Deuglo
Empowering Growth with Best Software  Development Company in Noida - DeugloEmpowering Growth with Best Software  Development Company in Noida - Deuglo
Empowering Growth with Best Software Development Company in Noida - Deuglo
Deuglo Infosystem Pvt Ltd
 
Vitthal Shirke Java Microservices Resume.pdf
Vitthal Shirke Java Microservices Resume.pdfVitthal Shirke Java Microservices Resume.pdf
Vitthal Shirke Java Microservices Resume.pdf
Vitthal Shirke
 
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdfAutomated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
timtebeek1
 
Graspan: A Big Data System for Big Code Analysis
Graspan: A Big Data System for Big Code AnalysisGraspan: A Big Data System for Big Code Analysis
Graspan: A Big Data System for Big Code Analysis
Aftab Hussain
 

Recently uploaded (20)

Measures in SQL (SIGMOD 2024, Santiago, Chile)
Measures in SQL (SIGMOD 2024, Santiago, Chile)Measures in SQL (SIGMOD 2024, Santiago, Chile)
Measures in SQL (SIGMOD 2024, Santiago, Chile)
 
OpenMetadata Community Meeting - 5th June 2024
OpenMetadata Community Meeting - 5th June 2024OpenMetadata Community Meeting - 5th June 2024
OpenMetadata Community Meeting - 5th June 2024
 
Unveiling the Advantages of Agile Software Development.pdf
Unveiling the Advantages of Agile Software Development.pdfUnveiling the Advantages of Agile Software Development.pdf
Unveiling the Advantages of Agile Software Development.pdf
 
LORRAINE ANDREI_LEQUIGAN_HOW TO USE WHATSAPP.pptx
LORRAINE ANDREI_LEQUIGAN_HOW TO USE WHATSAPP.pptxLORRAINE ANDREI_LEQUIGAN_HOW TO USE WHATSAPP.pptx
LORRAINE ANDREI_LEQUIGAN_HOW TO USE WHATSAPP.pptx
 
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian CompaniesE-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
 
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
ALGIT - Assembly Line for Green IT - Numbers, Data, FactsALGIT - Assembly Line for Green IT - Numbers, Data, Facts
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
 
Transform Your Communication with Cloud-Based IVR Solutions
Transform Your Communication with Cloud-Based IVR SolutionsTransform Your Communication with Cloud-Based IVR Solutions
Transform Your Communication with Cloud-Based IVR Solutions
 
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Neo4j - Product Vision and Knowledge Graphs - GraphSummit ParisNeo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
 
Hand Rolled Applicative User Validation Code Kata
Hand Rolled Applicative User ValidationCode KataHand Rolled Applicative User ValidationCode Kata
Hand Rolled Applicative User Validation Code Kata
 
Artificia Intellicence and XPath Extension Functions
Artificia Intellicence and XPath Extension FunctionsArtificia Intellicence and XPath Extension Functions
Artificia Intellicence and XPath Extension Functions
 
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI AppAI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
 
Energy consumption of Database Management - Florina Jonuzi
Energy consumption of Database Management - Florina JonuziEnergy consumption of Database Management - Florina Jonuzi
Energy consumption of Database Management - Florina Jonuzi
 
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Atelier - Innover avec l’IA Générative et les graphes de connaissancesAtelier - Innover avec l’IA Générative et les graphes de connaissances
Atelier - Innover avec l’IA Générative et les graphes de connaissances
 
Why Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise Edition
Why Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise EditionWhy Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise Edition
Why Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise Edition
 
What is Master Data Management by PiLog Group
What is Master Data Management by PiLog GroupWhat is Master Data Management by PiLog Group
What is Master Data Management by PiLog Group
 
KuberTENes Birthday Bash Guadalajara - Introducción a Argo CD
KuberTENes Birthday Bash Guadalajara - Introducción a Argo CDKuberTENes Birthday Bash Guadalajara - Introducción a Argo CD
KuberTENes Birthday Bash Guadalajara - Introducción a Argo CD
 
Empowering Growth with Best Software Development Company in Noida - Deuglo
Empowering Growth with Best Software  Development Company in Noida - DeugloEmpowering Growth with Best Software  Development Company in Noida - Deuglo
Empowering Growth with Best Software Development Company in Noida - Deuglo
 
Vitthal Shirke Java Microservices Resume.pdf
Vitthal Shirke Java Microservices Resume.pdfVitthal Shirke Java Microservices Resume.pdf
Vitthal Shirke Java Microservices Resume.pdf
 
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdfAutomated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
 
Graspan: A Big Data System for Big Code Analysis
Graspan: A Big Data System for Big Code AnalysisGraspan: A Big Data System for Big Code Analysis
Graspan: A Big Data System for Big Code Analysis
 

Software Project Requirement and Team Requirement Model

  • 1. Software Project Requirements with Project Team Member Requirement A MODEL FOR ALIGNING KAUSHAL MISHRA (MCA ) SRMGPC ,LUCKNOW
  • 2. Introduction What are the root causes that lead some project teams to operate well, while others struggle? Underperforming project teams may result from a weak change management plan, lack of talent on the project team, or insufficient stakeholder support, among other factors.  Many IT projects today have a project charter. Key components of a charter include the project scope, timeline, budget, approach and expected benefits.  All individuals related to the project want the best for the organization. However, when they see the project charter through their own prism, they may see the scope, the benefits and the approach quite differently. This is why it is critical to align early and often.
  • 3. What does a high-performance project team look like?
  • 4. Project Roles and Responsibilities Projects of different sizes have different needs for how the people are organized. In a small project, little organization structure is needed. There might be a primary sponsor, project manager and a project team.  Analyst : The Analyst is responsible for ensuring that the requirements of the business clients are captured and documented correctly before a solution is developed and implemented.  Change Control Board :The Change Control Board is usually made up of a group of decision makers authorized to accept changes to the projects requirements, budget, and timelines  Client: This is the people (or groups) that are the direct beneficiaries of a project or service. They are the people for whom the project is being undertaken.  Client Project Manager : If the project is large enough, the business client may have a primary contact that is designated as a comparable project manager for work on the client side.
  • 5. Project Roles and Responsibilities  Database Administrator: A Database Administrator is a specialist that models, designs and creates the databases and tables used by a software solution  Designer: The designer is responsible for understanding the business requirements and designing a solution that will meet the software needs.  Developer: The Developer is responsible for the actual building of the solution.  Project Manager: This is the person with authority to manage a project. This includes leading the planning and the development of all project deliverables. The project manager is responsible for managing the budget and schedule and all project management procedures (scope management, issues management, risk management, etc.)  Quality Manager : On a large project, quality management could take up a large amount of project management time.  Sponsor : This is the person who has ultimate authority over the project. The Sponsor provides project funding, resolves issues and scope changes, approves major deliverables and provides high-level direction.  Stakeholder : These are the specific people or groups who have a stake, or an interest, in the outcome of the project.  Suppliers / Vendors , Tester , Users
  • 6. Project Roles and Responsibilities Project Team : The project team consists of the full-time and part-time resources assigned to work on the deliverables of the project. This includes the analysts, designers, programmers, etc. They are responsible for:  Understanding the work to be completed.  Planning the assigned activities in more detail if needed.  Completing assigned work within the budget, timeline and quality expectations.  Informing the project manager of issues, scope changes, risk and quality concerns.  Proactively communicating status and managing expectations.
  • 7. How to Put together a high performance Team
  • 8. Project Team Requirment In most cases, an organization’s most valuable asset is its people. The same is true for project teams. Project success generally depends on individual talent, as well as team performance. Highly engaged and motivated teams are often more likely to perform at a high level and achieve their objectives.  Team members know each other well and understand everyone's strengths and weaknesses.  They genuinely respect and care about each other.  They believe in the organization’s mission and the projects objectives.  They celebrate successes and learn from failures.
  • 9. Provide High-Quality Leadership  Establish your team’s objectives and purpose – It’s important to verify that all team members know exactly what target they are aiming for and why it’s important to both the organization and the team. People may be more likely to work toward a common goal when they clearly understand its meaning and their contribution.  Establish a few rules – You can help build trust when you communicate what’s expected. It’s also generally a good idea to plan ahead in order to manage potential conflicts in a positive way.  Demonstrate trust – Allow people to take risks, experience failures and learn from their mistakes. Encourage creativity . You shouldn’t expect team members to put trust in you if you can’t first demonstrate that you trust them.  Require accountability – Regularly assess both team and individual performance. Deal with issues immediately by enforcing the established rules. Be sure to offer criticism constructively and privately. Without accountability, rules may be ignored, projects derailed and leaders may not respected.  Demonstrate your leadership – Model the work ethic, honesty, and level of communication and cooperation you expect. Show team members what success looks like, and they may be inspired to follow you.
  • 10. Recognize and Reward  People often like to be appreciated for a job well done. As a project leader, it's important to recognize team members when they meet important deadlines or achieve significant milestones. Praise from a leader can make team members feel appreciated, and may inspire the entire team to keep working toward the goal. However, keep in mind that not everyone may share the same enthusiasm for the spotlight. When you truly know your team well, you'll learn their preferences.
  • 11. Handle Delays Professionally  Work interruptions, technical troubles, additional responsibilities and unforeseen circumstances can delay a project. While they may be normal and expected in business, it doesn’t make missing a deadline any easier to swallow. Leadership is often judged by how people handle obstacles and delays, so make sure to do it professionally.  Start by evaluating the severity of the problem and remember that not every delay is a catastrophe. Next, assess how the delay may affect other aspects of the project, and what resources are available to shift to the problem. Finally, engage team members on finding and implementing the most effective solution. Also, make sure to keep appropriate stakeholders informed of the delay while providing an appropriate solution.  High-performing project teams can help make a project manager’s life easier. Start building your team by following these tips for improving project team performance. They're easy to implement and can pay off in a “dream team” that may help make projects more successful.
  • 12. Software Project Requirement The software requirements are description of features and functionalities of the target system. Requirements convey the expectations of users from the software product Requirement Engineering  The process to gather the software requirements from client, analyze and document them is known as requirement engineering.  The goal of requirement engineering is to develop and maintain sophisticated and descriptive ‘System Requirements Specification’ document.
  • 13. Requirement Engineering Process It is a four step process, which includes –  Feasibility Study  Requirement Gathering  Software Requirement Specification  Software Requirement Validation Let us see the process briefly -
  • 14. Feasibility study This feasibility study is focused towards goal of the organization. This study analyzes whether the software product can be practically materialized in terms of implementation, contribution of project to organization, cost constraints and as per values and objectives of the organization. It explores technical aspects of the project and product such as usability, maintainability, productivity and integration ability.  The output of this phase should be a feasibility study report that should contain adequate comments and recommendations for management about whether or not the project should be undertaken.
  • 15. Requirement Gathering and SRS If the feasibility report is positive towards undertaking the project, next phase starts with gathering requirements from the user. Analysts and engineers communicate with the client and end-users to know their ideas on what the software should provide and which features they want the software to include. Software Requirement Specification SRS is a document created by system analyst after the requirements are collected from various stakeholders.SRS defines how the intended software will interact with hardware, external interfaces, speed of operation, response time of system, portability of software across various platforms, maintainability, speed of recovery after crashing, Security, Quality, Limitations etc.
  • 16. Software Requirement Specification Requirements can be checked against following conditions -  If they can be practically implemented  If they are valid and as per functionality and domain of software  If there are any ambiguities  If they are complete
  • 17. Requirement elicitation process  Requirements gathering - The developers discuss with the client and end users and know their expectations from the software.  Organizing Requirements - The developers prioritize and arrange the requirements in order of importance, urgency and convenience.  Negotiation & discussion - If requirements are ambiguous or there are some conflicts in requirements of various stakeholders, if they are, it is then negotiated and discussed with stakeholders. Requirements may then be prioritized and reasonably compromised . The requirements come from various stakeholders. To remove the ambiguity and conflicts, they are discussed for clarity and correctness. Unrealistic requirements are compromised reasonably.  Documentation - All formal & informal, functional and non-functional requirements are documented and made available for next phase processing.  Requirements Elicitation is the process to find out the requirements for an intended software system by communicating with client, end users, system users and others who have a stake in the software system development.
  • 18. Requirement Elicitation Techniques  There are various ways to discover requirements Interviews: Structured (closed) interviews, where every single information to gather is decided in advance, they follow pattern and matter of discussion firmly (confidently). Non-structured (open) interviews, where information to gather is not decided in advance, more flexible and less biased. Oral interviews Written interviews One-to-one interviews which are held between two persons across the table. Surveys  Organization may conduct surveys among various stakeholders by querying about their expectation and requirements from the upcoming system.
  • 19. Requirement Elicitation Techniques Questionnaires:  A document with pre-defined set of objective questions and respective options is handed over to all stakeholders to answer, which are collected and compiled Brainstorming:  An informal debate is held among various stakeholders and all their inputs are recorded for further requirements analysis. Observation:  Team of experts visit the client’s organization or workplace. They observe the actual working of the existing installed systems. They observe the workflow at client’s end and how execution problems are dealt. The team itself draws some conclusions which aid to form requirements expected from the software.
  • 20. Aligning Modal Typically, alignment is required on three levels:  Sponsors and stakeholders—around the future state vision.  Management—around a plan that can be executed.  Project team—around priorities and tasks at hand.
  • 21. Sponsor and Stakeholder Alignment  Most executives feel that they see things the same way, especially when it comes to decisions that they made together. It is true that most projects are budgeted and start with consent from all appropriate executives. But does consent mean alignment? In reality, it’s likely that each executive wound up (tension) with their own unique vision of what will occur after the project is complete, and what it will take to successfully execute the project.  It is hard to convince executives to meet repeatedly to understand the changes that can push a project off target and to align their resources to the project goals. But this is the only way to stay on track and avoid wasting time on the rework that must will be required if team members take the project towards the misaligned future state visions in their department leads’ heads.
  • 22. Management Alignment  Middle management is cynical(selfish). They have seen these projects come and go. In fact, they say, we have more projects than we can keep track of right now. Yet, without a firm belief from middle management that a given project can and will be completed, you can count only on one thing—apathy( Nutral).  It may be tedious(Boring), but it’s well worth the effort to gather all relevant data that could impact the project’s success early on. This includes concerns, dependencies, vacations and other availability information. Chances are, some of that information is relevant to the project, some of it is good to know, and some of it is just fear of change. In all three cases, you want to hear it out and account for it .  Once the project plan has been adjusted to account for relevant data, people start believing that this is a real plan and you are not just going through the motions. After all, they have no more excuses to keep it from happening.
  • 23. Project Team Alignment  Most project teams consist of a core team (full-time participants) and an extended team (part-time participants). All of the members of the extended team and many of the core team members likely have other responsibilities in the organization, perhaps participating on other project teams. Not only are team members often distracted, but they each also have their own opinions about how the project should be conducted. It is very hard for a team to work in a coordinated fashion when each member has their own idea of how a given activity should be executed and their role in it.  There are many ways to align a project team around the approach: training the team in the methodology that is being used, team-building exercises, offsite workshops, communication programs, etc. All of these take time and effort, but they are well worth it. **********
  • 24. References 1. Abraic.in (Mikhail Papovsky @mpapov) Founder and CEO of Abraic, Inc. Dedicated to improving the outcomes of IT investments. 2. http://www.lifecyclestep.com/open/408.0LifecycleRoles.html (408.0 Project Roles and Responsibilities) 3. Reference paper : Robert Hans Tshwane University of Technology, Pretoria, South Africa hansr@tut.ac.za
  • 25. Presented By – KAUSHAL MISHRA