tag:blogger.com,1999:blog-7362727475792978259.post8862954272372057947..comments2023-03-27T03:58:05.111-07:00Comments on Effective Software Development: Good and bad about process improvementsAnonymoushttp://www.blogger.com/profile/03428406119776865921noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-7362727475792978259.post-56225843706301477602009-07-29T17:48:08.194-07:002009-07-29T17:48:08.194-07:00Good article Vladimir. I completely agree, without...Good article Vladimir. I completely agree, without measurment we cannot gauge if it is a process improvement or an overhead to the companyAnonymoushttps://www.blogger.com/profile/14209550835243191496noreply@blogger.comtag:blogger.com,1999:blog-7362727475792978259.post-71078586669839677542009-07-29T17:46:15.892-07:002009-07-29T17:46:15.892-07:00This comment has been removed by the author.Anonymoushttps://www.blogger.com/profile/14209550835243191496noreply@blogger.comtag:blogger.com,1999:blog-7362727475792978259.post-1499710679300464352009-07-27T00:10:28.333-07:002009-07-27T00:10:28.333-07:00Hi!
Asking which metric fits certain methodology ...Hi!<br /><br />Asking which metric fits certain methodology is not quite correct. The best way to establish metrics is to grow it from your needs. In Scrum they do post-mortem reviews where they find out root causes of why things went wrong and form the idea how they could do better in the future. Those ideas can be transformed into action plans. In result of execution of those actions you should see the changes. Metrics are needed to measure the change, to tell you whether you have improved and did it to the extent that you expected.<br /><br />For example, you may find out that it took a lot of resources to fix defects related to backend components. You know that there were 50 issues reported against backend. So, you decided to focus on unit testing of backend next release. Next release is about 0.5 of the previous in size, so you would expect 25 issues from backend if you have changed nothing. But you are expecting improvements to limit the number of issues to at least 5. Measuring the number of backend issues after the process you will find out whether the changes you ave made hit on target.<br /><br />Every improvement that you plan should have a measure that will tell you whether you are where you wated to be after the fact.<br /><br />Hope this helps! Feel free to ask more questions.Anonymoushttps://www.blogger.com/profile/03428406119776865921noreply@blogger.comtag:blogger.com,1999:blog-7362727475792978259.post-8143845461614623332009-07-26T01:31:25.536-07:002009-07-26T01:31:25.536-07:00There is no process in my office at present. But n...There is no process in my office at present. But now the management wants to define a process. In my previous job we followed Agile and scrum as tool. So I want to establish scrum. Can you suggest me which metrics are the vital for scrum and a reference for those metrics?Nusrathttps://www.blogger.com/profile/00839400971144020126noreply@blogger.com