Skip to main content

Day 13

Today I spent my time creating a new JIRA project to move three of the teams into - and attempting to redesign the workflow, fields, and in general simplify it while keeping it so it matches the process and will allow us to report on what is important to us.

My goal is to get it cleaned up and ready so that on Monday during sprint planning the three targeted teams can begin by using the new project.

In addition, I am going to start cleaning (matching pattern) the SharePoint, and create a template with links to relevant data for each customer. The objective is to make things self-service and predictable which will help with onboarding as well as assisting as analysts and developers move team to team.

Finally, I hope to create common definitions and agendas for rituals. For example an agenda for the retrospective, and define our Story Points so there is a common understanding between teams about what a "3" is, for example, I am getting some pushback on this. Mostly in the "we did this before" but when I say that's great show me the documents! The scrum masters do not have any. They currently do not see the value in this. Hopefully, I can better articulate the value in everyone having common terms and patterns.

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