IBM Targetprocess

Targetprocess

A place for Targetprocess product users to learn, connect, share and grow together.

 View Only
Back to discussions
Expand all | Collapse all

Spikes in TP

  • 1.  Spikes in TP

    Posted Mon February 21, 2022 11:51 AM
    Hi,

    I'm wondering how you guys have implemented spikes in TP.

    I see 2 possibilities :
    • add a flag/custom field to an existing core entity (e.g. user story)
      • pro : fits in the parent-child topology of epic/capability/feature/us/task
      • contra : 
        • no possibility to see it as a specific entity
        • one needs to know what to filter on, when trying to distinguish from a user story
        • same (possibly) complex set of states as user story
        • us has story points, while a spike does not
    • create a new ExD entity
      • pro : fully tweakable and distinguishable from the other entity types
      • contra :
        • does not fit with other core entities in a list view
        • does not fit in the parent-child topology of epic/capability/feature/us/task
    Jan
    #Targetprocess


  • 2.  RE: Spikes in TP

    Posted Tue February 22, 2022 01:43 AM
    Edited by Arno van Herk Tue November 05, 2024 05:32 PM
    Hi Jan,
    I would go for option 1 as this is already quite possible in TP. "The Work Type" als to specify the type of work, eg Business, Enabler, Maintenance, Research& Design. You can add more values if desired. 
    This solution allows spikes to be part of the normal setup in TP as the Work Type field can be used in filtering/color coding etc.
    I would disagree with your statement that a Spike has no story points. Although a Spike is not part of the committed deliverables as identified and agreed upon in the PI Planning event, the Spike does require resources of eg a team, hence is influncing the team's capacity. Like other stories, spikes are put in the Team Backlog, estimated, and sized to fit in an iteration.
    Best regards,Arno
    Original Message


  • 3.  RE: Spikes in TP

    Posted Tue February 22, 2022 02:39 AM
    Hi Arno,

    I tried to defend option 1, but users don't like the contra's
    TP is really missing the possibility to add new core types (cfr in Jira you can easily create new issue types)

    Jan
    Original Message


  • 4.  RE: Spikes in TP

    Posted Tue February 22, 2022 02:59 AM
    Hi Jan, 
    We see the same happening with Jira users. The freedom they have to just define anything, results in all kinds of different ways of working on team levels. This is going to bite you when moving up towards portfolio management and bringing together things on a higher level.
    Also, repeating my previous statement, not sizing spikes is actually creating a lot of hidden work which will hinder solid planning.
    The way we implement TP is not just about implementing a tool, but also about professionalizing agile working. Sometimes this requires painfull decisions to keep the frogs in the bucket.
    Best regards,Arno
    Original Message


  • 5.  RE: Spikes in TP

    Posted Wed February 23, 2022 02:04 AM

    I've done quite some pushing back on this Arno.
    Unfortunately, the tendency is to give 'freedom' to the teams...

    Nevertheless, I'm still convinced that the tool should be able to cope with this and provide a new native entity.

    People - Processes - Tools, not the other way around.... :/

    Jan


    Original Message


  • 6.  RE: Spikes in TP

    Posted Wed February 23, 2022 02:31 AM

    Hi Jan,

    Would it be acceptable for the teams to create User Stories or Features of Work type Spike (similar to worktype Business, Enabler, etc.)  and allow them to not assign any estimation to these?


    You wouldn't need a new entity and provide flexibility to the teams whether to size these or not.

    Just a suggestion, if I misunderstood the issue, then ignore my reply.

    Best regards,
    Edwin



    ------------------------------
    Edwin Schumacher
    Synergio B.V.
    Managing Partner
    e.schumacher@synergio.nl
    ------------------------------

    Original Message


  • 7.  RE: Spikes in TP

    Posted Wed February 23, 2022 02:47 AM
    Hi Jan,
    For one of our customers we have (had) created a extra itemtype called "Dependency". This sits on the level of Feature and we can include this without problems on lists and boards that show both Features and Dependencies. Not sure why your need would not be possible using the extended domain model, as I have not been involved of course in your discussions with TP/Apptio. 
    Should your case have reached the limits of TP, then the good news is that Jira allows the freedom for the teams, so if that is critical maybe stick with Jira. When I dont want to get wet driving to work, I take my car and not my bike.
    Best regards,Arno
    Original Message


  • 8.  RE: Spikes in TP

    Posted Wed February 23, 2022 03:54 AM

    Indeed Arno.

    We also have created ExD entities that are linked to others.
    Problem here is that, you are limited to adding entities to a board, once a ExD entity is referenced.

    If e.g. you create a spike ExD entity, then you can't add it to a board where you see vertically the team iterations, horizontally the features, and use userstories, bugs and spikes as cards.
    Spikes don't fit in the parent-child hierarchy of the core items. Once you have features as horitontal lanes, team iterations as vertical lanes, you can only see userstories and bugs as cards.

    Jan


    Original Message


  • 9.  RE: Spikes in TP

    Posted Tue February 22, 2022 03:12 AM
    Hi Jan,

    Find more information on Spikes here: https://www.scaledagileframework.com/spikes/

    Best regards,
    Edwin

    ------------------------------
    Edwin Schumacher
    Synergio B.V.
    Managing Partner
    e.schumacher@synergio.nl
    ------------------------------

    Original Message


  • 10.  RE: Spikes in TP

    Posted Tue February 22, 2022 03:51 AM

    Tx Edwin.

    I'm SAFe RTE and SPC certified, so I was aware of the definition :)

    I'm just looking for a nice implementation in TP, which is - to my opinion - not the case (yet).

    Jan


    Original Message


  • 11.  RE: Spikes in TP

    Posted Wed February 23, 2022 01:55 AM
    For those of us with almost no background on SAFe, this was a good reference. Thanks, @Edwin Schumacher!​

    ------------------------------
    Regards, Guillermo
    ------------------------------

    Original Message


  • 12.  RE: Spikes in TP

    Posted Wed February 23, 2022 04:03 AM

    Hi All

    Great to see discussions like this evolving here, especially on a useful and common topic like this one.

    We've quickly put together a blog post on the topic here, highlighting the simplest of solutions (custom field tag) but would like to explore the possible extra value from Extended Domains in the future, and how they relate to different agile approaches to spikes, and integrations with, of course, Jira - so please keep the thoughts flowing!

    Especially interesting is any variation to the objectives of view, track progress, track effort, measure value.

    Thanks again,

    Thodi


    Original Message


  • 13.  RE: Spikes in TP

    Posted Wed February 23, 2022 04:21 AM

    @Thodi Andersson

    There are 2 things :
    - how to modal the spike in TP : customize a current entity of create a new one.
    - attributes of a spike

    What's your proposal to tackle these 2 ?

    Jan

    ​
    Original Message


  • 14.  RE: Spikes in TP

    Posted Wed February 23, 2022 06:07 AM

    Hi Jan

    So what decisions do you want to facilitate, from how you manage spikes, so as to maximise value (i.e. ensure alignment to objectives, maximise productivity, maximise creativity, guarantee quality)?

    This, and if your definition of a spike varies from the standard, should drive things.

    For example:

    • ELT want to know what spikes were done for which business objectives. (To confirm alignment, show investigation).
    • Head of Innovation wants to know what proportion of time are we spending on spikes (this is a measure of agile adoption / innovation).
    • Teams should see what each person in the team is working on in an iteration, be it spike or non-spike (right people on right job, collaboration).

    So maybe start with what value is missed out on by using tagged User Stories for spikes in the model? (As per the blog post).

    What use cases cannot be fulfilled?

    Is this sub-optimal value significant in the overall business context / decision making framework?

    If it is significant then the more complex alternatives / variations (like ED) can be considered and assessed to see if 'the juice is worth the squeeze'. 

    (Of course please do ping me or set up a meeting when suits and we can look at your exact situation, comments here are for general guidance and may not fit your specificities!)

    Kind regards

    Thodi


    Original Message