2. TOPICS TO BE DISCUSSED
JIRA
• COCOMO
• RISK FACTORS
3. JIRA
• JIRA is a popular project management tool used by software development
teams to plan, track, and manage their work. It offers a variety of features
such as issue tracking, agile boards, project reporting, and integration with
other software tools.
• It is a part of Atlassian's suite of software development tools, which also
includes Bitbucket for code collaboration and deployment, and helps for
team collaboration and documentation.
4. COCOMO
• COCOMO (COnstructive Cost Model) is a software cost estimation model
that is typically used to estimate the effort, time, and cost required to
develop a software project.
• To use COCOMO, we would need to identify the project's characteristics,
such as size, complexity, and development team size. You would also need
to define the requirements, the technology, and the development schedule.
Based on these inputs, COCOMO would estimate the effort and cost
required for the project's development.
5. COCOMO ON JIRA
In order to apply COCOMO to estimate the cost of a software project
using JIRA, we will need to consider the following factors:
• Size of the project: we can use the number of issues, bugs, or features
that need to be developed.
• Complexity of the project: we can use the number of custom fields,
workflows, and integrations required.
6. • Development environment: Uses the hardware and software required to
run JIRA, as well as any plugins or add-ons required.
• Development team: We can use the number of developers required,
their experience in using JIRA, and their productivity.
7. JIRA using the Basic COCOMO model:
• Size of the project: 50 KLOC
• Development mode: Organic
• Labor rate: $50/hour
• Number of resources: 5
Effort = a * (KLOC)^b
a = 2.4, b = 1.05 for Organic mode
Effort = 2.4 * (50)^1.05 = 135 person-months
Cost = Effort * Labor Rate
Cost = 135 * $50 = $6,750
Therefore, based on the information we have, the estimated effort required to develop the
software using JIRA is 135 person-months, and the estimated cost of the project is $6,750.
8. RISK FACTORS ON JIRA
Data security risks: As with any software tool that stores sensitive data, there is
always the risk of data breaches, hacking, or other security vulnerabilities.
Organizations should take steps to ensure that their JIRA instance is secured and
up to date with the latest security patches.
Integration risks: JIRA integrates with many other tools and platforms, such as
source control systems, CI/CD pipelines, and issue tracking systems. If these
integrations are not properly configured or maintained, it can cause issues and risks
to the project.
9. Performance risks: JIRA can become slow or unresponsive if it is not properly
optimized or if there is a large amount of data in the instance. Organizations should
monitor their JIRA instance's performance and take steps to optimize it as needed.
User adoption risks: JIRA has a lot of features and can be overwhelming for some
users, which can lead to low adoption rates or user frustration. Organizations should
provide proper training and resources to help users understand and use JIRA
effectively.
Vendor dependency risks: JIRA is a proprietary tool owned by Atlassian, which
means organizations are dependent on Atlassian for support and updates. If
Atlassian were to discontinue support for JIRA, organizations would need to find an
alternative solution.
