Advertisement

Management Guidelines for Database Developers’ Teams in Software Development Projects

  • Lazar Rusu
  • Yifeng Lin
  • Georg Hodosi
Part of the Communications in Computer and Information Science book series (CCIS, volume 49)

Abstract

Worldwide job market for database developers (DBDs) is continually increasing in last several years. In some companies, DBDs are organized as a special team (DBDs team) to support other projects and roles. As a new role, the DBDs team is facing a major problem that there are not any management guidelines for them. The team manager does not know which kinds of tasks should be assigned to this team and what practices should be used during DBDs work. Therefore in this paper we have developed a set of management guidelines, which includes 8 fundamental tasks and 17 practices from software development process, by using two methodologies Capability Maturity Model (CMM) and agile software development in particular Scrum in order to improve the DBDs team work. Moreover the management guidelines developed here has been complemented with practices from authors’ experience in this area and has been evaluated in the case of a software company. The management guidelines for DBD teams presented in this paper could be very usefully for other companies too that are using a DBDs team and could contribute towards an increase of the efficiency of these teams in their work on software development projects.

Keywords

database developers’ teams agile software development capability maturity model management guidelines software development project 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Beck, K., Andres, C.: Extreme Programming Explained: Embrace Change, 2nd edn., p. 19. Addison-Wesley Professional, Reading (2004)Google Scholar
  2. 2.
    Beck, K., Beedle, M., Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., Grenning, J., Highsmith, J., Hunt, A., Jeffries, R., Kern, J., Marick, B., Martin, R.C., Mellor, S., Schwaber, K., Sutherland, J., Thomas, D.: Manifesto for agile software development (2001), http://www.agilemanifesto.org/ (accessed on October 21, 2008)
  3. 3.
    Bern, A., Pasi, A., Nikula, U., Smolander, K.: Contextual Factors Affecting the Software Development Process - An Initial View. In: The Second AIS SIGS and European Symposium on Systems Analysis and Design, Gdansk, Poland, June 5 (2007)Google Scholar
  4. 4.
    Börjesson, A., Martinsson, F., Timmerås, M.: Agile improvement practices in software organizations. European Journal of Information Systems 15, 169–182 (2006)CrossRefGoogle Scholar
  5. 5.
    Carnegie Mellon Software Engineering Institute. Capability Maturity Model Integration (CMMISM), Version 1.1, pp. 11–14 (2002), http://www.sei.cmu.edu/pub/documents/02.reports/pdf/02tr012.pdf (accessed on October 2008)
  6. 6.
    Cockburn, A.: Crystal Clear: A Human-Powered Methodology for Small Teams. Addison-Wesley Professional, Reading (2004)Google Scholar
  7. 7.
    Cockburn, A., Highsmith, J.: Agile software development: The people factor. IEEE Computer 34, 131–133 (2001)Google Scholar
  8. 8.
    Coffin, R., Lane, D.: A Practical Guide to Seven Agile Methodologies, Part 1 (2006a), http://www.devx.com/architect/Article/32761 (accessed on October 21, 2008)
  9. 9.
    Coffin, R., Lane, D.: A Practical Guide to Seven Agile Methodologies, Part 2 (2006b), http://www.devx.com/architect/Article/32836/0/page/1 (accessed on October 21, 2008)
  10. 10.
    Dyba, T.: Improvisation in small software organizations. IEEE Software 17, 82–87 (2000)CrossRefGoogle Scholar
  11. 11.
    EI Group: Database developer (2008), http://www.schoolsintheusa.com/careerprofiles_details.cfm?carid=466 (accessed on October 21, 2008)
  12. 12.
    Eriksson, L.T., Wiedersheim-Paul, F.: Att utreda, forska och rapportera, 6th edn. Malmö, Liber Ekonomi (1999)Google Scholar
  13. 13.
    Fritzsche, M., Keil, P.: Agile Methods and CMMI: Compatibility or Conflict? e-Informatica Software Engineering Journal 1(1) (2007), http://www.e-informatyka.pl/e-Informatica/attach/Issue1/Vol1Iss1Art1eInformatica.pdf (accessed on October 27, 2008)
  14. 14.
    Gladstein, D.L.: Groups in context: A model of task group effectiveness. Administrative Science Quarterly 29, 499–517 (1984)CrossRefGoogle Scholar
  15. 15.
    Info-tech research group: Database Developer Info-Tech Advisor: Job Description (2009), http://www.infotech.com/ITA/Research%20Centers/Data%20,-a-,%20Digital%20Assets/General/Database%20Developer.aspx (accessed on October 27, 2008)
  16. 16.
    Jalote, P.: CMM in Practice: Processes for Executing Software Projects at Infosys, p. 195. Addison-Wesley Professional, Reading (1999)Google Scholar
  17. 17.
    Miller, A.: Distributed Agile Development at Microsoft Patterns & Practices. Microsoft (2008), http://download.microsoft.com/download/4/4/a/44a2cebd-63fb-4379-898d-9cf24822c6cc/distributed_agile_development_at_microsoft_patterns_and_practices.pdf (accessed on April 9, 2009)
  18. 18.
    OdinJobs.com, SQL developer Job Market Overview (2008), http://www.odinjobs.com/Sql-developer_job_market_overview.html (access on March 20, 2009)
  19. 19.
    Paulk, M.C., Weber, C.V., Curtis, B., Chrissis, M.B.: The Capability Maturity Model: Guidelines for Improving the Software Process, pp. 3–4, 32, 39, 133, 180, 213. Addison-Wesley Professional, Reading (1994)Google Scholar
  20. 20.
    Perks, M.: Best practices for software development projects (2006), http://www.ibm.com/developerworks/websphere/library/techarticles/0306_perks/perks2.html (access on March 20, 2009)
  21. 21.
    Petty, C.: Gartner Says Worldwide Relational Database Market Increased 14 Percent in 2006, Gartner Inc. (2007), http://www.gartner.com/it/page.jsp?id=507466 (accessed on October 27, 2008)
  22. 22.
    Poppendieck, M., Poppendieck, T.: Lean Software Development: An Agile Toolkit. Addison-Wesley, Reading (2003)Google Scholar
  23. 23.
    Rising, L., Janoff, N.S.: The Scrum software development process for small teams. IEEE Software 17, 26–32 (2000)CrossRefGoogle Scholar
  24. 24.
    Salas, E., Cooke, N.J., Rosen, M.A.: On Teams, Teamwork, and Team Performance: Discoveries and Developments. Human Factors: The Journal of the Human Factors and Ergonomics Society 50(3), 540–547 (2008)CrossRefGoogle Scholar
  25. 25.
    Salas, E., Sims, D.E., Burke, C.S.: Is there a "big five" in teamwork? Small Group Research 36(5), 555–599 (2005)CrossRefGoogle Scholar
  26. 26.
    Schwaber, K.: Agile Project Management with Scrum, p. 138. Microsoft Press (2004)Google Scholar
  27. 27.
    Wang, X., Vidgen, R.: Order and chaos in software development: a comparison of two software development teams in a major IT company. In: European Conference on Information Systems 2007, pp. 816–817 (2007)Google Scholar
  28. 28.
    Yin, R.K.: Case Study Research: Design and Methods, 3rd edn. Sage Publications, Thousand Oaks (2003)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  • Lazar Rusu
    • 1
  • Yifeng Lin
    • 2
  • Georg Hodosi
    • 1
  1. 1.Royal Institute of TechnologyStockholm UniversityStockholmSweden
  2. 2.Bwin Games AB 

Personalised recommendations