Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Structured Anal...  Code Repository Policy
Previous Previous
 
Next Next
New Post 5/12/2019 11:40 AM
Informative
User is offline Ktynna
1 posts
No Ranking


Code Repository Policy  

Hi Team,

I need help with preparing a code repository policy document

 
New Post 1/27/2020 7:22 AM
User is offline Stewart F
110 posts
7th Level Poster


Re: Code Repository Policy  

Hi Ktynna,

I realise that quite some time has passed since you posted this, but thought I would answer in case anyone else had a similar problem.

I am surprised to be honest that this has been assigned to a BA to do. In reality, it is a Developer requirement and I would have thought they were best to set it up and use it? However, in the name of being a good BA I will give some advice. 

As with any other system/Requirement project for a BA, you need to understand who your Stakeholders are and arrange to talk to them. Without knowing the set-up of your company that you work for, I would guess that your best bets are the Head of Development and the Lead Developer (if there is more than one then invite them all to one workshop). 

Ask them what they expect to place in their (yes it will be code - but what rules about code will it be?), how people should access the repository and who has access to it. 

Then ask them what steps need to happen for each of these. For example, in order to put code into the repository, does that code need to be signed off by anyone?

Next, ask them how they would access it specifically. For example, what search parameters would they use/want? Do they want each piece of code to have a title so that they are easier to find? How long does the code stay in the repository before it is auto-purged? Do they want it auto-purged and if so, what rules do they want you to follow?

They will obviously need some form of UI In order to search for code. I would suggest keeping it simple. Time is short and Devs typically give up if they cant find anything in 30 seconds. The use of Tags might be useful here as well. Maybe the original Code owner, so they could go and speak to them (if they are still with the company)?

Once done, write your BRD or User Stories depending on your methodology used, in the same way as usual. Just because the project is for internal Users doesn't affect how you run it from your perspective.

Then proceed as usual.  

I think that covers everything. It does kind of depend on the answers to some of the questions above, but typically I would go with what I have said.  

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Structured Anal...  Code Repository Policy

Community Blog - Latest Posts

There are big differences between data exploration versus data presentation. And you need to be aware of these differences as you're creating data stories and data presentations. Let’s start by defining our terms: Data exploration means the deep-dive analysis of data in search of new insights. Data presentation means...
Is Agile a reason to avoid documentation? I bet this question shows up again and again while working with product requirements. On one side, we have got long specifications, complicated diagrams, mystical technical design, too many prototypes and pretty obvious for engineers user guides (do we really need so much?). On the other side, can we actual...
The cloud-native application development has helped enterprises all around the globe reduce time-to-market, enhance performance, and develop agility and flexibility. Several enterprises are achieving these results by migrating their systems or traditional monolithic applications to the cloud. But to gain from the real benefits of cloud technology, ...

 






 

Copyright 2006-2022 by Modern Analyst Media LLC