search

nikantonelli / PortfolioItemTimeLine

Timeline for portfolio items with dependency strings & drag'N'drop positioning
MIT License
5 stars 5 forks source link

Limited to 20 children? #12

Open Adderfly-Mark opened 2 years ago

Adderfly-Mark commented 2 years ago

Hi Nik and Andrew, first let me thank you for building a great and very useful app. I wish Rally had this built in. In general it works fine however we have noticed that there appears to be a limit of 20 children. We have a hierarchy of Initiative - Opus - Feature - Story. Whenever we specify Initiative Opus or Feature we only ever get back the first 20 children (e..g A Feature with 25 user stories will only show 20 of them on your Timeline, likewise an Opus with > 20 Features will only have the first 20 shown). I have scoured the code (I'm not a great coder like you guys) and cannot find a clear reason for it. Any ideas? Any help greatly appreciated. Best regards, Mark Harris (markfwharris@gmail.com)

nikantonelli commented 2 years ago

Hi Mark, The 20 limit is imposed by Rally when you don't specify your page size. There is a maximum of something like 2000 if you do specify it. In the code where I have control over it in the Ext storeConfig, I have made the pageSize to be 50, 200 and 2000 ( e.g. https://github.com/nikantonelli/PortfolioItemTimeLine/blob/d261e5bbd73681af37c159ac878b7daa2e372095/App.js#L2051) as appropriate.

However, fetching the UserStories underneath a Feature (and all the children fetching too) is done using the GET function here: https://github.com/nikantonelli/PortfolioItemTimeLine/blob/d261e5bbd73681af37c159ac878b7daa2e372095/worker.js#L57 I suspect the url could be modified to have a "pageSize=200" option on it.

As I haven't worked for Rally for some time now, I don't have access to the sdk.js (or sdk-debug.js) file to help you further with the correct format of the request.

As a matter of Agile practice, it is my belief that 20 Stories below a Feature is not a good idea. I have always recommend that a Feature has 5-9 stories max. If it needs more, then split the Feature. Or if you need to record more 'bits', then use Tasks underneath Stories. I would extend that also to the portfolio item hierarchy: 20 children is too many for a single item. Basically, you are saying that your items are huge and hard to define so I'm just going to list lots of bits.

There is a important reason for saying to limit children numbers by splitting. If you get your organisation to think in these terms, you are more likely to understand the size and complexity of the work you are undertaking and more likely to be on-target , on-time, consistent, reliable. This makes your planning easier and you, more successful.

Adderfly-Mark commented 2 years ago

Thanks for the reply and the info about the code Nik, much appreciated as I know coming back to past code is often a headache. I'll experiment with the tips you gave and see how far I can get. As for best practice on Features etc I am aware of this and agree wholeheartedly with you, however I am a very hands-on Agile coach who is now working in a huge bank with huge initiatives and less than ideal agile practices from long before I joined, I can't see them changing their malpractices anytime soon so I'm looking for tools such as this to make the situation clear to them and their mistakes visual. I do like your app. Best regards and thanks again, Mark.