Skip to main content

Root Cause Analysis

I find doing a Root Case Analysis (RCA) in the spirit of Retrospective is a great way to look at an event or project in a non-blaming way to find areas to improve (reducing waste and iterative improvement are key to a healthy agile team).

A tool to help with this can be a fishbone diagram

read more here:
http://whatis.techtarget.com/definition/fishbone-diagram

Following our rocky data center migration, I am performing this to find ways to make the next one is smoother.

The key thing is to ask for and get "issues" not "solutions" and dig into the many possible causes, and from there the many possible ways to improve or prevent or detect earlier the issue.

Comments

Post a Comment

Popular posts from this blog

How do I find the Custom Field ID in Jira Cloud?

So you need to find the Custom Field ID in Jira Cloud. Perhaps you need the ID for a custom field to work on soem code, an API call or a script. How do you find it? You can find the ID in the URL when managing custom fields Jira - Settings - Issues - Fields - Custom Fields https://***.atlassian.net/secure/admin/ViewCustomFields.jspa Select "Edit" on the desired custom field .../admin/EditCustomField!default.jspa?id=12802 There you go! It is that number at the end of the URL Alternately, you can use ScriptRunner Jira - Setttings - Add-ons - Script Runner - Script Console and run the following def issueKey = '***-####' def result = get('/rest/api/2/issue/' + issueKey)         .header('Content-Type', 'application/json')         .asObject(Map) if (result.status == 200){     return result.body.fields } else {     return "Failed to find issue: Status: ${result.status} ${result.body}"
Post a Comment
Read more

When Hiring (Job Posts)

I know this is not about Agile specifically but I wanted to share how I craft Job Posts when hiring, I would love to continue to improve my process. When writing a Job Post I do the following; Have boilerplate about the company itself. Yes, the candidate should dig more but you want them to want to apply and want to research. Describe the Role, where the department fits within the company, what the team/departments purpose is, and what normal activities the job will encompass. Indicate the type of person/passions which would work well List requirements , real requirements, this should be 5 or less, these should be demonstrable items Demonstrable - Upbeat attitude is not easy to demonstrate, for example Always have alternatives to a major! Great technical people can have humanities majors – i.e. use “or equivalent experience” List bonuses/ nice to have /additional items that a candidate would benefit by having Explain the benefits of the company (should be boilerplate tal
1 comment
Read more

Sprint Planning - Poker

Here are some free resources I plan to try for sprint planning. Let me know what you think if you enjoy doing planning poker as your given method of story-pointing and try these or have others to recommend. http://www.votingpoker.com http://firepoker.io/#/ https://www.pointingpoker.com/ https://scrumpoker.online/ https://play.planningpoker.com/plans https://scrumpoker.online/ https://tools.wmflabs.org/hatjitsu/
1 comment
Read more