Skip to main content

Creating Stories and Tasks in Jira: Personas and our Software Development Team

Part of the CI/CD Development Series

The next step is developing who is on our hypothetical development team. Given that it has a React front end and ColdFusion as the Server Side language, I came up with the following personas, all of which have their own needs and considerations for our development environment. I've listed all the jobs that need doing, not the people involved since, even on a small team or a team of one, these "hats" are all worn by someone, even if it's the same person.

Personas for our Project

Dev Ops Coordinator - The person responsible for smooth and accurate deployments

CF Developer - The person responsible for the API and fulfillment code development and maintenance.

React Developer - The person responsible for the front end development

Database Coordinator - The person responsible for the schema, data, up time and, presumably the testing databases used by the developers.

Lead Developer - The person responsible for coordinating the developers and, presumably, on boarding new team members.

Project Manager - Responsible for schedules, budget and documentation

Product Manager - The key advocate for the business cases and the product

End User - The person who is going to be ultimately using the app we create. At the moment, we have no idea who this is since, in essence, at the moment, the app itself is playing a second tier role to it's architecture and the development process for the sake of our project but since this is our ultimate audience, even for this experiment, they need to be here.

With these roles in mind we can start to do some diagramming and ticket writing.

Further Reading and source material
https://this.isfluent.com/blog/2018/roles-and-responsibilities-in-a-software-development-team
https://www.atlascode.com/blog/software-development-project-roles-and-responsibilities/
https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/


Labels:

Comments

  1. Laura BushNovember 19, 2021 at 11:57 PM

    You have shared a lot of information in this article. I would like to express my gratitude to everyone who contributed to this useful article. Keep posting. software company in bangladesh

    ReplyDelete
  2. VidhyamenonDecember 9, 2021 at 3:29 AM

    Great Blog with Good Information.

    Jira Training
    Jira Training in Bangalore

    ReplyDelete
  3. JuzApps Pte LtdMarch 1, 2022 at 12:20 PM

    I just need to say this is a well-informed article which you have shared here about hoodies. It is an engaging and gainful article for us. Continue imparting this sort of info, Thanks to you. Software Development Company in Singapore

    ReplyDelete
  4. John ClarkApril 14, 2022 at 10:17 PM

    You have provided valuable data for us. It is great and informative for everyone. Keep posting! also look at this Bill.com Competitors and Alternatives. I am very thankful to you.

    ReplyDelete
  5. XebrioMay 28, 2022 at 12:57 AM

    Clearly, It is an engaging blog for us that you have provided here about Project Development Software This is a great resource to enhance our knowledge about it. Thank you.

    ReplyDelete
  6. Alia parkerOctober 1, 2022 at 10:06 PM

    There are many benefits of social media marketing. One of the most important benefits is that it allows businesses to connect with their customers on a personal level. This is because social media marketing allows businesses to interact with their customers directly. This interaction can help businesses to understand their customers better and to build better relationships with them. social media management company Chicago

    ReplyDelete

Post a Comment

Popular posts from this blog

As the Dev Ops Manager, I need to start planning our CI/CD release process

Part of the CI/CD Development Series Once we have our Deployment Diagram designed, we need to figure out out to get from here to there. If the end point is the appropriate server environment, the starting point is the developer with his/her hand on the keyboard. These steps take place on a variety of machines, within various process and can changes based on what files are checked in or not. At the moment, we've only created the early basics as seen below. The Beginning of our Deployment Activity Chart Even though there is quite a long way to go there are some elements which we have already been determined. For example We have determined the broad strokes of our technology stack. This is going to be React on the front end and ColdFusion on the server side. We have determined that we are going to be using linting on both the CF and React paths. CFLint for the CF and ESLint for the Javascript We have determined that we are going to be formatters - CFFormat for CF and...
Post a Comment
Read more

As the Dev Ops Coordinator, I need to set up our git repo into several branches with the appropriate permissions for each one

Part of the CI/CD Development Series The core of every CI/CD process is the code repository whether it be Git, Mercurial, SVN or whatever. The general idea is that it allows multiple developers (or whomever) to access your code in the appropriate way in the appropriate level. This can either be the ability for anyone to pull an open source project but not write to the repo directly or full access to a developer on your team to create branches, push to master or anything that needs doing. For our project, we're using git although the hosting provider was up for discussion between Github, Bitbucket by Atlassian or CodeCommit on AWS. We decided to go with AWS for two reasons. 1. We are going use other tools in AWS as part of the build so we decided to keep it all together. 2. We needed to solidify the ins and outs of using IAM for the process. Basic Steps Create the Repo Create the branches we need Use IAM to apply the appropriate permissions to each branch and to set up ...
1 comment
Read more