tag:blogger.com,1999:blog-5494767799799842634.post3071658867006983222..comments2011-12-19T12:09:56.718-08:00Comments on Agile Shmagile: Technical Debt - from Owing to OwningAvi Naparstekhttp://www.blogger.com/profile/01162363912283088140noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-5494767799799842634.post-26376056356859037952011-12-19T12:09:56.718-08:002011-12-19T12:09:56.718-08:00Just wanted to share a conversation sparked by fee...Just wanted to share a conversation sparked by feedback from André Brissette on the LinkedIn <br />Agile Coaching group<br /><br />Thanks André!<br />--------------------------<br /><br /><br /><br /><br />On 12/17/11 8:51 AM, André Brissette wrote: <br />-------------------- <br />Hi Avi, here is some feedbacks <br /><br />Your article is too long. many elements are very valuable in your article. But in my opinion people are used to (or only have time for) read smaller article. What you could do is to break it in multiple article with title like: <br /><br />1) Owing technical debt is owing something to both the PO and to the team itself. (I love this one :-) <br />2) Type of technical debt <br />3) Responsibility and Ownership of the debt <br />4) etc.. <br /><br />Another reason for breaking it down in multiple articles is to facilitate conversation with your readers. For example, in the section "Type of debt" they were many points that I wanted to comment or argue. But by the end of the article, my focus was distracted by other (interesting) elements. I think people are more likely to comment on shorter article. <br /><br />by the way, it looks you have a typo here "In this perspective the tam is not only responsible for ..." <br /><br />It is a very interesting article and it looks like you know your subject well. good work! <br /><br />have a nice day, <br />André<br /><br /><br /><br /><br />On 12/17/11 11:18 AM, Avi Naparstek wrote: <br />-------------------- <br />Hi André, and thanks for the constructive and honest feedback! <br /><br />I see what you mean by it being too long.. And you make excellent reasons for breaking it down. <br /><br />To be honest I was rather eager to get it out - I've just published it in some more forums so I'm not sure I'll be re-editing it, but will be sure to take that in mind for the following posts. If it's OK with you I'll want to credit you for giving me that feedback. <br /><br />I guess it's also a matter of media as you pointed out - in a magazine or academic publication a long article might be appropriate, whereas in a blog-post published in forums for discussion a shorter one would be more effective. I definitely owe you one for giving me that observation :)<br /><br />...And you are right about the typo of course, I just ran a spell-check and found some more.. Yikes! <br /><br />So thanks again, I would be interested nevertheless in hearing your thoughts, comments and arguments in the group. Maybe a good discussion will come out of it after all. <br /><br />Best wishes, <br />Avi <br /><br /><br />On 12/19/11 6:45 AM, André Brissette wrote: <br />-------------------- <br />Hi Avi, <br /><br />Of course credit is always welcome :-) If you want we can put this exchange public. I initially choose to make it private as my comments were more on the form than the content. <br /><br />I checked the thread this morning and it looks that you spark an interesting discussion, <br />thank for the initiative! <br /><br />Happy holidays to you and your family, <br />Andre <br /><br /><br /><br /><br /><br />On 12/19/11 Avi Naparstek wrote: <br />-------------------- <br />Thanks.. <br /><br />I just skimmed through the conversations - I was glad to see you participated. I've yet to have a deeper look at what was written. <br /><br />And I am actually glad you commented about the form - it's just as valuable and is a rarer kind o feedback to get. <br /><br />I appreciate the fact that you feedbacked privately, although with some courage.. hmm.. . scrum? courage? why not? here goes... <br /><br />Happy holidays to you too and to everyone how will be reading this! <br />AviAvi Naparstekhttps://www.blogger.com/profile/01162363912283088140noreply@blogger.com