tag:blogger.com,1999:blog-15466608.post4141477509704690114..comments2009-11-22T21:30:08.878+11:00Ted Hardynoreply@blogger.comBlogger5125tag:blogger.com,1999:blog-15466608.post-76758665900079093242009-11-22T21:30:08.878+11:002009-11-22T21:30:08.878+11:00Hi all, thanks for the comments.<br /><br />David - The degree of up front work yeilds different value outcomes depending on the cirumstances. New post coming up this week on that topic.<br /><br />Josh - I am not sure the product backlog and WBS need to be that tightly linked, but agree with the sentiment. In a fixed scope project I think the requirements MUST be represented in the WBS.<br /><br />Pawell - I appreciate the inclination to pay for performance but what about the principle of optimising the whole rather than the parts?Craig Brownhttp://www.blogger.com/profile/01210437173582289473noreply@blogger.comtag:blogger.com,1999:blog-15466608.post-23610778786105623312009-11-22T10:16:11.516+11:002009-11-22T10:16:11.516+11:00Кто знает где реально качнуть Хрумер 5.0 Палладиум???<br />очень надо...<br />оч незаменимый инструмент для сеошника да и не только... все советуют. Помогите!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-15466608.post-43102175156061462352009-11-20T21:20:54.663+11:002009-11-20T21:20:54.663+11:00It would be a problem but I left salary-strictly-connected-with-role-name approach long ago. It&#39;s all about how much the company is willing to pay for work someone does, no matter what they have on their business card.<br /><br />In last company we had only one role in development team - it was called, surprise, surprise, developer. And believe me salaries was spread really wide (you could earn up to three time as much without changing a role).<br /><br />In current company approach is different - we have tons of role names which at the end of the day means the same - a developer. But it works the same - if you compare compare salary of junior programmer to senior software expert the difference is similar. We just keep changing role names as crazy ifsomeone is good enough to be paid more.<br /><br />HR doesn&#39;t have to understand and I don&#39;t really expect them to. As far as I&#39;ve enough power to hire right people for decent and satisfying salary that&#39;s all OK. And I couldn&#39;t care less how their role is called and what isprinted on their business cards.Pawel Brodzinskihttp://blog.brodzinski.comnoreply@blogger.comtag:blogger.com,1999:blog-15466608.post-78813091435772897172009-11-19T15:44:15.716+11:002009-11-19T15:44:15.716+11:002 things:<br /><br />1) I see a triangle between the WBS, requirements, and the product backlog and traceability between the three using the WBS ID as essential. There&#39;s going to be correlation between requirements and the product backlog as things get re-prioritized. Do you implement it this way?<br /><br />2) On the pay issue, I get a little sick of the defined roles, especially when they are so close and overlap. Pay should be based on the value added. In my mind HR in general has it all wrong; we should be doing wage cuts when people are under-performing and giving raises commensurate with the value being added. Let&#39;s go to a hybrid commission model!<br /><br />So a scrum team that releases quality software in half the time another department can....that difference should show up in the paychecks!<br /><br />Josh Nankivel<br /><a href="http://pmStudent.com" rel="nofollow">pmStudent.com</a>Joshhttp://www.blogger.com/profile/06798222298277681691noreply@blogger.comtag:blogger.com,1999:blog-15466608.post-38648850439724769092009-11-19T14:21:12.039+11:002009-11-19T14:21:12.039+11:00Craig, how are ya...<br /><br />I keep trying to have a discussion about Scrum, topic being &quot;where do the requirements, or product backlog, come from?&quot; <br /><br />One answer I have got is that it comes from &quot;Up-front work&quot;. Sounds a lot like what I do as a BA...David Wrighthttp://www.blogger.com/profile/05103379078232846587noreply@blogger.com