Can anyone describe the difference in the "Item Type" values in a the DCO Sizing spreadsheet for specifications?
Can anyone describe the difference in the "Item Type" values in a the DCO Sizing spreadsheet for specifications?
***Updated by moderator: Lochan to add Categories***
***Updated by moderator: Lochan to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
US
User Story
– Identifies the effort necessary to implement an Atomic piece of work in the
Scrum Methodology that can easily be
managed and meet the definition of done within a single Scrum sprint. A User Story describes work that still
remains to be completed and does not include scope that has already been
implemented.
New Specification –
Identifies the effort necessary to implement an Atomic piece of work in the
Agile/BPM Methodologies. This type of
Specification assumes no prior work has been completed and that the effort
needed is to build or complete tasks associated with a new capability. A Specifications scope is usually defined by
the actions a single actor would take with a much larger process.
Existing Specification
– Indicates the reuse of a capability that already exists in the
system through an out of the box feature or from a previous development effort is being identified. There should be little to no effort in using
this capability as it will be used as is.
Extend Existing
Specification – is an Atomic Piece of work in an Agile/BPM
Methodology. This type of Specification
assumes that an existing capability is being modified in some way and that the
work being described will be a modification to that existing capability.
User Story
– Identifies the effort necessary to implement an Atomic piece of work in the
Scrum Methodology that can easily be
managed and meet the definition of done within a single Scrum sprint. A User Story describes work that still
remains to be completed and does not include scope that has already been
implemented.
New Specification –
Identifies the effort necessary to implement an Atomic piece of work in the
Agile/BPM Methodologies. This type of
Specification assumes no prior work has been completed and that the effort
needed is to build or complete tasks associated with a new capability. A Specifications scope is usually defined by
the actions a single actor would take with a much larger process.
Existing Specification
– Indicates the reuse of a capability that already exists in the
system through an out of the box feature or from a previous development effort is being identified. There should be little to no effort in using
this capability as it will be used as is.
Extend Existing
Specification – is an Atomic Piece of work in an Agile/BPM
Methodology. This type of Specification
assumes that an existing capability is being modified in some way and that the
work being described will be a modification to that existing capability.
New WorkType –
Identifies the effort necessary to create a new PRPC WorkType
Existing WorkType – Indicates
that a previously existing Work Type is to be used and that no additional
effort will be necessary to access this Worktype
Extend Existing
WorkType – Identifies the effort necessary to modify an existing
WorkType to include new characteristics.
This assumes that the WorkType exists in some form prior to this effort
being undertaken.
Supporting Type –
No effort is associated with this item, it is purely for categorizing
Specifications and will not instantiate into any PRPC artifact.
Business Rules
Specification – Identifies the effort required to facilitate the
instantiation of business rules inside of PRPC such as decision tables.
Business Specification
– Identifies the effort necessary to implement a non-Atomic
piece of work in the Agile/BPM Methodologies.
This type of Specification assumes no prior work has been completed and
that the effort needed is to build or complete tasks associated with a new
capability. Business Specifications
normally describe the entire process from creation to resolution and therefore
are normally bigger in scope than a standard Specification which looks at a
segment of work associated with a single actor.
Pegasystems Inc.
IN
Hi Morris, Good Morning!
Kindly ignore the post if the item type doesn't fall in the below sample categories...
- Alternative
- Correspondence
- Decision
- Flow
- Human based step (Assignment)
- Integration
- Primary Path
- Report
- Stating process/screen
- Sub process
- Automated step
the tied/associated spec with the above item type would let the end/business user about the implementation like "How the requirement is implemented"
example: for processing chargeback...
- user would like to do as a straight through processing without back officer involvement.
- for such requirement a decision based Automated step (using utility) will be implemented
to reflect the implementation on the spec document, the item type for the spec would be associated with Automated step.
Please share your thoughts/comments, Thank you!
psahukaru
Pegasystems Inc.
US
Hi Psahukaru,
The Item type in the sizing spreadsheet is not the same as the Type field on Specification rules. The Item type in the sizing spreadsheet that Gavin is asking about contains values such as User Story, New Specification, Existing Specification, Extend Existing Specification, New WorkType, Existing WorkType, etc.
Pegasystems Inc.
US
Hi Gavin,
Those values are defined within the spreadsheet itself, so Richard Fay would know the original intent. Overall, though, that column is trying to allow the user a chance to identify each row usefully, however they want.
Pegasystems Inc.
GB
Richard, hi…
I have posted a question on the Mesh that it seems you are the man to answer âº
It may be good for you to answer on the Mesh as I couldn’t find any useful info in it - and nothing on the PDN!
https://mesh.pega.com/message/179218?et=watches.email.thread#179218
Regards
Gavin Morris | Pegasystems Ltd | <uk.linkedin.com/in/gavinmorris/>
Head Office: One Reading Central, 23 Forbury Road, Reading, Berkshire, RG1 3JH
Mobile: +44 (0) 7895 906991 | Office: +44 (0) 1189 591150 (Ext 4712) | Fax: +44 (0) 1189 591174
E-Mail: [email protected]<mailto:[email protected]> | Build for Change® | www.pega.com<http://www.pega.com/> | https://twitter.com/pega
Richard, hi…
I have posted a question on the Mesh that it seems you are the man to answer âº
It may be good for you to answer on the Mesh as I couldn’t find any useful info in it - and nothing on the PDN!
https://mesh.pega.com/message/179218?et=watches.email.thread#179218
Regards
Gavin Morris | Pegasystems Ltd | <uk.linkedin.com/in/gavinmorris/>
Head Office: One Reading Central, 23 Forbury Road, Reading, Berkshire, RG1 3JH
Mobile: +44 (0) 7895 906991 | Office: +44 (0) 1189 591150 (Ext 4712) | Fax: +44 (0) 1189 591174
E-Mail: [email protected]<mailto:[email protected]> | Build for Change® | www.pega.com<http://www.pega.com/> | https://twitter.com/pega
PegaCan | Evolve Your CRM | www.pega.com/PegaCan<http://www.pega.com/PegaCan>
Pegasystems Inc.
GB
Looks like Richard is the man to talk to then!
The current list :-
- User Story
- New Specification
- Existing Specification
- Extend Existing Specification
- New WorkType
- Existing WorkType
- Extend Existing WorkType
- Supporting Type
- Business Rules Specification
- Business Specification
While the breakdown may be different there is little difference between the "User Story" and "New Specification" - but you dont have "Existing" or "Extend" for User Story - I'm not sure what qualifies as a "Business Rule Specification" or indeed when a "Specification" becomes a "Business Specification"...
I will see if I can get Richard to reply to this post...
Accepted Solution
Pegasystems Inc.
US
User Story
– Identifies the effort necessary to implement an Atomic piece of work in the
Scrum Methodology that can easily be
managed and meet the definition of done within a single Scrum sprint. A User Story describes work that still
remains to be completed and does not include scope that has already been
implemented.
New Specification –
Identifies the effort necessary to implement an Atomic piece of work in the
Agile/BPM Methodologies. This type of
Specification assumes no prior work has been completed and that the effort
needed is to build or complete tasks associated with a new capability. A Specifications scope is usually defined by
the actions a single actor would take with a much larger process.
Existing Specification
– Indicates the reuse of a capability that already exists in the
system through an out of the box feature or from a previous development effort is being identified. There should be little to no effort in using
this capability as it will be used as is.
Extend Existing
Specification – is an Atomic Piece of work in an Agile/BPM
Methodology. This type of Specification
assumes that an existing capability is being modified in some way and that the
work being described will be a modification to that existing capability.
User Story
– Identifies the effort necessary to implement an Atomic piece of work in the
Scrum Methodology that can easily be
managed and meet the definition of done within a single Scrum sprint. A User Story describes work that still
remains to be completed and does not include scope that has already been
implemented.
New Specification –
Identifies the effort necessary to implement an Atomic piece of work in the
Agile/BPM Methodologies. This type of
Specification assumes no prior work has been completed and that the effort
needed is to build or complete tasks associated with a new capability. A Specifications scope is usually defined by
the actions a single actor would take with a much larger process.
Existing Specification
– Indicates the reuse of a capability that already exists in the
system through an out of the box feature or from a previous development effort is being identified. There should be little to no effort in using
this capability as it will be used as is.
Extend Existing
Specification – is an Atomic Piece of work in an Agile/BPM
Methodology. This type of Specification
assumes that an existing capability is being modified in some way and that the
work being described will be a modification to that existing capability.
New WorkType –
Identifies the effort necessary to create a new PRPC WorkType
Existing WorkType – Indicates
that a previously existing Work Type is to be used and that no additional
effort will be necessary to access this Worktype
Extend Existing
WorkType – Identifies the effort necessary to modify an existing
WorkType to include new characteristics.
This assumes that the WorkType exists in some form prior to this effort
being undertaken.
Supporting Type –
No effort is associated with this item, it is purely for categorizing
Specifications and will not instantiate into any PRPC artifact.
Business Rules
Specification – Identifies the effort required to facilitate the
instantiation of business rules inside of PRPC such as decision tables.
Business Specification
– Identifies the effort necessary to implement a non-Atomic
piece of work in the Agile/BPM Methodologies.
This type of Specification assumes no prior work has been completed and
that the effort needed is to build or complete tasks associated with a new
capability. Business Specifications
normally describe the entire process from creation to resolution and therefore
are normally bigger in scope than a standard Specification which looks at a
segment of work associated with a single actor.