When Acquia’s Global Support Team outgrew their ticketing system in 2013, it was time to make a change.
There are plenty of tools that can improve your efficiency, but they can become burdens rather than real helpers.
Recently I began working on a D8 module, but this isn't a story about a D8 module. The work I did provided me an opportunity to get back to my pre-Drupal object oriented (OO) roots.
Identity theft and site compromises are all-too-common occurrences -- it seems a day rarely goes by without a news story detailing the latest batch of user passwords which have been compromised and
In business, technology is a means to an end, and using it effectively to achieve that end requires planning and strategy.
The Capability Maturity Model, designed for assessing the formality of a software development process, was initially described back in 1989. The Forrester Digital Maturity Model is one of several models that update the CMM for modern software development in the age of e-commerce and mobile development, when digital capability isn't an add-on but rather is fundamental to business success. The model emphasizes communicating strategy while putting management and control processes into place.
Drupal is an incredibly flexible and expressive CMS and development framework. As a
It seems as if almost every Web developer hates using JIRA. Many developers feel it’s tedious, time-consuming work and they’d rather do just about anything else.
But JIRA doesn’t have to feel that way. With the help of some easy-to-learn shortcuts, you can use JIRA more efficiently and have time to do something you enjoy. In fact, these shortcuts are all but guaranteed to make you like JIRA more – or maybe hate it a lot less.
I recently reviewed the shortcuts with Acquia’s India team, and developers there couldn’t thank me enough for simplifying things. As you probably know, JIRA provides bug and issue tracking and project management functions. In other words, it’s useful and often necessary – something not to be avoided.
Kanban and Scrum are two different methodologies that can be utilized within your development organization. Both have pros and cons as agile methodologies, and one is often suited to a certain project better than the other. Let’s explore the definitions, differences, and how to utilize them practically for your next development project.
Kanban is a model of continuous slating, or continuous improvement. Essentially, when utilizing kanban, project priorities can change in real time, based on what takes priority at a certain time, so there is a certain flow to the work. Requirements can be added and clients or internal stakeholders can change their minds at any given time throughout the life of the project.
Like a composer who can’t wait to conduct a great symphony, I couldn’t wait to get my hands on Composer, a PHP dependency management tool.