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

More on Site Architecture / CI/CD / and Repos

We're starting to move from the high level overview and more into the details of our project.  Architecture We established that we using React as our front end technology and ColdFusion as our server side. At a more granular level, we'll be using React with Redux for our front end app and we want our server side to be not just "ajax" enabled but a true REST API. To this end, we're going to incorporate Coldbox from Ortus Solutions. Repos These two code bases have different needs, and possibly locations, when they are deployed. As a result, we're going to have two repositories: one for the React and another for the API. This will allow us to keep our code separated and cleaner all the way through to deployment.  For each of these repos, we'll follow the procedure we laid out previously with the MASTER branch being used to deploy to production and a DEVELOPMENT branch being used for active work which is then fed into the Master branch via pull requests.  Test...
Post a Comment
Read more

CF: Scripting amidst the tags

Recently I had to do a quick "utility" page where I needed to see how many files from a directory listing had been recorded into a database. I've been writing about 98% of my CF code in script syntax but, since it was quick and easy, I did this quickly in tags because it was outputting directly to the browser. In doing so, I made an interesting discovery in that, when you use closures, even in tag based pages, you can write cfscript. Here's the example Get the directory listing:  < cfset alljs = directoryList(expandpath( '/src' ), true , "path" , "*.js" )> Get the database listings and convert it to an array < cfquery name = "alljsQ" datasource = "blah" > select * from sitefiles where filename like '%.js%' </ cfquery > < cfset recordedFiles = valuelist(alljsQ.filename).listToArray()> Use a filter function to weed out the files I'd already recorded < cfset missingFiles = alljs.fi...
Post a Comment
Read more