Skip to main content

Day 12-15

I worked to create, and simplify a new jira project.

My goal was I to only keep only the fields we used.

We also changed the workflow (the statuses issues flow through) and added a new issue type.

The most frustrating part was the bulk updates of the backlog and in progress to the new project.

For now
Issue types
Epic-a project that will span may sprints
Story-A piece of work I can deliver that has value
Task-something that needs to be done to accomplish the story
Request something someone asked for and we haven't backlogged and prepped yet
Bug - a defect

Issue status
Requested a request we have not looked at
Accepted - a request we will do, in the future
To be groomed - may get rid of but we are prepping this for intake
Grooming - we are breaking it up/down
Groomed-will get rid of
To do - ready
In progress - being done
Completed-done
Rejected not done (no longer needed, indefinite hold, duplicate, whatever)

Comments

Post a Comment

Popular posts from this blog

What is Agile and How Can I Use it Well?

I gave a talk at BSidesLV 2018 In the "Proving Ground" track for new speakers "What is Agile and How Can I Use it Well?" Are you a person who works with Agile developers? Are they driving you nuts? This presentation will explain the core tenets of Agile and how they apply to you, the security wonk. What you may not realize is that at its core Agile is about delivering a product, fast. Agile teams are focused on delivering a minimal viable product, getting feedback, and improving both the product and the process through iterative and continuous improvement. With a keen understanding of Agile forged in the trenches of large deployments, this presentation shows you how to effectively scale your team in order to have security be an integrated part of the Agile iterations. Slides: https://docs.google.com/presentation/d/1sCM5si8UxtOusDlBeecXudstDf9idDFQWadhLtMHPpg/edit#slide=id.p Be sure to read the speaker's notes! Video: https:// youtu...
1 comment
Read more

The dreaded "Clone" in Jira

Jira Cloud Scrum Teams Case: We clone template issues, as our work is repetitive, and get “clone” in the summary and it makes it hard to read. Built-In Jira allows you to remove "Clone" from the story you are cloning, but if you are also copying the sub-tasks there is not the option to remove it. There are ways to turn this off in Jira Server, but I could not find it in Jira cloud. Solution: Jira - Settings - Add-Ons - ScriptRunner - Escalation Service The Escalation Service called: Remove Clone In Summary As this user: (myself) Checked - enabled On this schedule: Every Hour For first 50 results returned by this query:  Project in (pipe) and Summary ~ "CLONE" Will run this code:  // check if issue.fields.summary looks like "CLONE -" def updatedSummary ="" if (issue.fields.summary.startsWith("CLONE -")) {     //if so, modify issue.fields.summary to not suck.     updatedSummary = issue.fields.summar...
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