Selling Centralized Project Management Solutions

• xsevensinzx

  One Orange Chip

  Points: 25560

  More actions

  October 2, 2014 at 9:42 pm

  #293912

  Hello!

  As a new guy to SQL Server and database development with only a year of experience in the field, I've had number of questions pop up during my time in the field. One that has came up recently is not particularly specific to SQL Server, but relates because that's the area I work in every day. So, I figured a good place for that question is in the newbie section of the forums because I'm more than certain a large number of you guys have faced this already.

  That said, I come from a software development background. That's how I landed in databases. I have always worked in and around databases from a developer perspective. So, I have the background to jump into the database world versus someone who has never worked with databases before.

  However, just because I have dabbled in databases and can program in a few different languages, it doesn't mean I am a DBA or a database developer. I respect the field and have always made a clear distinction between the two in a world where sometimes it becomes blurred for some silly reason that I will never be able to understand.

  The reason I'm explaining all of this is because with databases, it gets a bit funky, especially with source control. In my background, you always have it. The same goes for centralized project management or issue tracking solutions such as JIRA. The same also goes for internal wikis to document code and whatnot.

  This get's a bit more crazy when working as a lone database or IT guy in a company of non IT related roles. Thus leads to my question and problem. How do you justify to a team of non-tech related team members to jump on board with using centralized project management and issue tracking solutions such as JIRA?

  I ask because I have never faced an issue with that in software development. It was always a given. But now that I am not working primarily in a company that does not do software development, it's a bit harder to sell things like JIRA where I still need their feedback on database related development tasks. Tasks such as complex reports and the works.

  Right now, I've been using solutions such as JIRA by myself. My goal is to get more team members using it where they can know what's on my plate while also having a good communication channel to provide feedback on future tasks that involve both the database and their work.