Menu

Tree [1460f1] master /
 History

HTTPS access


File Date Author Commit
 src 2015-12-11 Kris Ramanah Kris Ramanah [4c9728] initial commit
 .gitignore 2015-12-11 Kris Ramanah Kris Ramanah [1460f1] Updated documentation in reademe file.
 LICENSE 2015-12-11 Kris Ramanah Kris Ramanah [4c9728] initial commit
 README 2015-12-11 Kris Ramanah Kris Ramanah [1460f1] Updated documentation in reademe file.
 pom.xml 2015-12-11 Kris Ramanah Kris Ramanah [4c9728] initial commit

Read Me

# Resulting Technical Debt - Atlassian Plugin #

## Problem statement: ##

* On too many projects quick wins are preferred over accurate design and development, resulting in clients actually paying a number of times the actual cost that was agreed on.

* Broadly speaking, this is like stealing from the customers.

* The worst part of this is that the actual people who choose to go the 'quick win' way, rarely get blamed of it and the closest scape goats are always the 
    * The contractors : hell they are no longer here....it must be them
    *  The Devs : they coded it...who else do we blame
    *  The QAs : why didn't they check that this before ???
                 

Anyway, the reason I started to work on this plugin a while ago is because the client deserves to know what choice is being made and the cost that they are ready to bear.

If a client is ready to accept that in the interest of time, they are ok to get a software which will cost 3 times more because of a decision that is being made now Then fair enough, its an informed decision.


## Description ##

This Jira plugin will be used to tag a requirement/design/documentation with a Technical debt cost.

* For a particular project, the aggregate of the technical debt can then be calculated and give a clear picture of the cost impact that a company will need to bear for that project.

* The rating will be in man days and the amount will be calculated based on the current cost of roles required.

* The admin screen will provide the ability to add the costs for each type of role.

* When technical debt of a particular project will be tagged, an approximate figure (in terms of man days)
will need to be attributed against each role that will need to be involved to fix this debt or to carry on without this debt
e.g GM (4d), SM(4d), Dev(20d), Test(20d), DBA(20d)   
 

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.