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.
On ne peut généralement pas le prévoir. Parfois, on en prend connaissance à la dernière minute. Mais cela peut aussi être le moment le plus attendu de l’année. Quel que soit le contexte, toutes les sociétés sont confrontées un jour ou l’autre à une situation dans laquelle une défaillance de leur site aurait un effet dévastateur.
Dans cette série d’articles, nous revenons sur l’expérience de trois des plus importants clients d’Acquia. Avec un accent tout particulier sur la préparation technique et opérationnelle, l’amélioration continue, les caractéristiques de la plateforme et l’importance de toujours écouter les retours.
Thanks for coming back. If you tried a few of the tips in the first part of this series, you probably realized that making a website accessible to all visitors doesn’t require much time, or cause much stress. Even if you didn’t yet try, I hope this blog further illustrates that clients need not worry about sitting down themselves to create a website that’s useful and informative to visitors with disabilities - without reaching out to a developer for help.
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.
Most advice to improve Drupal site performance is aimed at developers and DevOps folks. In reality, many Drupal sites are built by site builders using flexible Drupal modules rather than custom code.
In this blog series, we will give site builders the knowledge and tools to enhance the performance of their web sites, without ever touching PHP or the command line.
The Drupal community is already rich in modules and best practices that can significantly improve the performance of any Drupal site. Now it’s time to take advantage of the community’s hard work!