3.18.

1 User Stories

User User Task Point Team

Story Stories (Hour) Member
Number

1.
2.
3.
4.
5. As a project
Create Database
manager, I
want to be
able to easily UI/Design
view the sprint
burnout chart
for each sprint, Program
so that I can
1
quickly
identify Test
potential
problems or
issues that
need to be
addressed.
 1. As a team
member, I Create Database
want to be
able to update
the actual line UI/Design
2 of the sprint
burnout chart
each day, so Program
that the chart
accurately
reflects the Test
progress of
the team.

1. As a project
manager, I
Create Database
want to be
able to adjust
3 the ideal line
UI/Design
of the sprint
burnout chart
based on
Program
changes in
team capacity
or other
Test
factors, so that
the chart
reflects
realistic
expectations
for the sprint.
 1. As a team
member, I Create Database
want to be
able to view
the sprint UI/Design
4 burnout chart
for each sprint,
so that I can Program
see how much
work we have
completed Test
and how much
work remains
to be done.

1. As a project
manager, I Create Database
want to be
able to set
5 alerts or UI/Design
notifications
for the sprint
burnout chart, Program
so that I am
notified if the
actual line falls Test
below the
ideal line or
exceeds it,
indicating
potential
problems.
 1. As a
stakeholder, I Create Database
want to be
able to view
the sprint UI/Design
burnout chart
6 for each sprint,
so that I can Program
track the
progress of
the project Test
and ensure
that it is on
track to meet
its goals.
2.

1. As a team
member, I
want to be Create Database
able to
collaborate
with my UI/Design
colleagues and
discuss the
7 sprint burnout Program
chart, so that
we can identify
potential Test
problems and
work together
to find
solutions.
3.18.2 Information Security

Information Security involves ensuring that the chart is protected from unauthorized access or
tampering, whether it's in digital or physical form. It involves implementing measures to
safeguard the data, such as using secure project management tools, limiting access to
authorized personnel, password-protecting files, and encrypting communication channels.

In addition, information security requires ensuring the confidentiality, integrity, and availability
of the data. This means that the data should be kept confidential from unauthorized parties,
accurate and reliable, and available to the authorized parties when needed.

1. Use secure tools: Choose a secure project management tool or software to create and
store your sprint burndown chart. Ensure that the software has appropriate security
features such as user authentication, access controls, and encryption.

2. Limit access: Limit access to the sprint burndown chart to team members and
stakeholders who need it. Ensure that each user has the appropriate level of access
based on their role in the project.
 3. Password protect: If you are sharing the sprint burndown chart via email or other file-
sharing services, password protect the file to prevent unauthorized access.

4. Back up regularly: Back up the sprint burndown chart regularly to prevent loss of data.
Store backups securely to prevent unauthorized access.

5. Update software regularly: Keep your project management software up to date with the
latest security patches and updates.

6. Train users: Train team members on the importance of information security and how to
protect sensitive data, including the sprint burndown chart.

7. Use secure communication channels: When communicating about the sprint burndown
chart or other sensitive project information, use secure communication channels such as
encrypted email or messaging services.

3.18.3 EIS Standard

Introduction
Purpose and objectives of the EIS standard: The purpose of the EIS (Enterprise Integration
Standard) standard is to provide a set of guidelines and best practices for integrating software
systems and exchanging data in an enterprise environment. The objectives of the EIS standard
include improving data quality, reducing integration costs and risks, and increasing operational
efficiency.

Scope of the EIS standard: The EIS standard applies to all software systems and data exchange
processes within the enterprise. It covers data modeling, messaging protocols, security, data
exchange formats, interfaces, implementation, and compliance.

Definitions of key terms and concepts: The EIS standard uses the following key terms and
concepts:
Integration: The process of connecting different software systems and enabling data exchange
between them.

Data modeling: The process of creating a logical data structure that represents the entities and
relationships within the enterprise.

Messaging protocols: The set of rules and standards that govern the exchange of messages
between software systems.

Security: The measures and controls implemented to protect enterprise data and systems from
unauthorized access, use, disclosure, disruption, modification, or destruction.

Data exchange formats: The standard syntax and structure for exchanging data between
software systems.

Interfaces: The point of interaction between software systems or between a system and its users.

Compliance: The adherence to regulatory and industry standards and guidelines.

Data modeling

Standards for data modeling in sprint: The EIS standard requires that data modeling in sprint be
based on a common set of standards and guidelines that ensure data consistency, integrity, and
quality across the enterprise. The data model should be designed in such a way that it can be
easily extended or modified to accommodate changes in the enterprise.

Guidelines for data structure, relationships, and integrity: The EIS standard provides guidelines
for designing the data structure, defining the relationships between entities, and maintaining
data integrity. These guidelines ensure that data is consistent, accurate, and complete.

Best practices for data mapping and transformation: The EIS standard recommends best
practices for mapping data from one system to another, transforming data to conform to a
common data format, and validating data to ensure its accuracy and completeness.

Messaging protocols

Standards for messaging protocols in sprint: The EIS standard requires that messaging protocols
in sprint be based on a common set of standards and guidelines that ensure interoperability,
reliability, and security of data exchange between systems. The messaging protocols should be
designed in such a way that they can be easily extended or modified to accommodate changes
in the enterprise.

Guidelines for message format, syntax, and semantics: The EIS standard provides guidelines for
defining the message format, syntax, and semantics to ensure consistency and compatibility
across the enterprise. These guidelines ensure that messages are easy to interpret and process
by different systems.
Best practices for message routing and delivery: The EIS standard recommends best practices for
routing messages between systems, ensuring message delivery, and handling message errors.

Security

Standards for security in sprint data and systems: The EIS standard requires that security in
sprint data and systems be based on a common set of standards and guidelines that ensure
data confidentiality, integrity, and availability. The security measures should be designed in such
a way that they can be easily extended or modified to accommodate changes in the enterprise.

Guidelines for access control, authentication, and authorization: The EIS standard provides
guidelines for access control, authentication, and authorization to ensure that only authorized
users have access to sensitive data and systems. These guidelines ensure that the enterprise is
protected from unauthorized access and data breaches.

Best practices for data encryption and protection: The EIS standard recommends best practices
for encrypting sensitive data, protecting data at rest and in transit, and ensuring

3.18.4 EIS Integration

EIS integration is a complex process that involves various stages, stakeholders, and technologies.
Here is a detailed overview of the EIS integration process:

1. Planning Stage:

The planning stage involves defining the objectives and requirements of the EIS integration
project. The following steps are involved:

 Define the scope of the EIS integration project and identify the stakeholders involved.
 Conduct a feasibility study to assess the viability of the project.
 Define the requirements of the EIS integration project, including functional and non-
functional requirements.
 Identify the existing IT infrastructure, including hardware, software, and network
components.
 Identify the potential risks and challenges of the EIS integration project and develop
mitigation strategies.
2. Design Stage:

The design stage involves developing a detailed plan for integrating the EIS into the existing IT
infrastructure. The following steps are involved:
  Define the EIS integration architecture, including the integration components and data
flows.
 Identify any necessary hardware and software components for the integration project.
 Develop a detailed data mapping plan that specifies how data will be transferred
between the EIS and existing systems.
 Identify any necessary customizations to the EIS or existing systems to enable
integration.
 Define the security and access control measures to ensure the confidentiality, integrity,
and availability of data.
3. Development Stage:

The development stage involves building and testing the integration components and
customizations. The following steps are involved:

 Build the integration components, including connectors, APIs, and middleware.

 Develop any necessary customizations to the EIS or existing systems.
 Test the integration components and customizations to ensure they function correctly
and meet the requirements of the project.
 Perform unit testing, integration testing, and system testing to verify the functionality
and performance of the integrated system.
4. Deployment Stage:

The deployment stage involves rolling out the integrated system to the organization. The
following steps are involved:

 Install the integration components and customizations on the appropriate systems.

 Migrate the data from the existing systems to the EIS.
 Train end-users on how to use the EIS and any new features or functionality.
 Provide ongoing support to end-users and address any issues or concerns that arise.
5. Maintenance Stage:

The maintenance stage involves providing ongoing support and maintenance to ensure the
continued functionality and performance of the integrated system. The following steps are
involved:

 Monitor the performance of the integrated system and address any issues or concerns
that arise.
 Perform regular maintenance activities, such as backups, updates, and patches.
  Evaluate the effectiveness of the integrated system and identify any areas for
improvement.
 Implement any necessary changes or enhancements to the integrated system to improve
its functionality and performance.

3.18.5 Analytic

Analytics Report

Executive Summary:

The Sprint Burn-down Chart analytics report provides insights into the performance of the sprint
team and helps to identify areas of improvement. The report includes a summary of the sprint
progress, analysis of team velocity, and recommendations for future sprints.

Sprint Progress:

The Sprint Burn-down Chart shows that the team has made steady progress throughout the
sprint. However, there were a few instances of missed deadlines which led to a decrease in
velocity. Overall, the team was able to complete 85% of the sprint backlog within the allocated
time.

Team Velocity:

The team velocity was calculated based on the number of story points completed during each
sprint. The team had an average velocity of 20 story points per sprint, which is below the
expected velocity of 25 story points per sprint. This indicates that the team needs to improve its
efficiency to meet the expected velocity.
Recommendations:

Based on the analysis, the following recommendations are provided for future sprints:

Improve sprint planning: The team needs to focus on better sprint planning to ensure that
deadlines are met and the expected velocity is achieved.

Increase team efficiency: The team needs to identify areas where efficiency can be improved and
implement strategies to optimize team performance.

Review the sprint backlog: The sprint backlog needs to be reviewed to ensure that it is feasible
and realistic, and that it aligns with the project goals.

Conclusion:

In conclusion, the Sprint Burn-down Chart analytics report provides valuable insights into the
performance of the sprint team and identifies areas of improvement for future sprints. By
implementing the recommendations provided in the report, the team can improve its efficiency,
meet deadlines, and achieve its goals.