Developers must have good feedback to ensure productivity. Most shops have a continuous integration (CI) build process that allows the developer to quickly know if a build failed, and some shops have an automatic deploy of the CI build to provide website feedback. Lance Lyons writes about an approach to automating the update of databases in a CI environment.
One of the hardest daily tasks developers, QA, ScrumMasters, and product owners encounter is effective communication with others. Sound implausible? According to many articles, research, and personal observations, the main cause of project failure is not technology or hardware, but inefficient communication stemming from lack of effective communication between team members, incomplete business analysis, imprecise requirements, and vaguely formulated business objectives.
Leslie Sachs discusses the key people skills essential to appreciating how and which personality factors most impact one's ability to successfully implement core build and release management practices.
Agile's core principles may have been originally intended at the software development, but the concept of DevOps has shown that agile's benefits can be experienced by a much larger audience. Collaboration between these two departments benefits just as much as anyone.
How does personality impact the implementation of industry Standards and Frameworks? It would seem that following the guidance in the IEEE 828 CM Planning standard is simply a matter of writing CM Plans and documenting your existing CM practices. The fact is that some people implement Standards and Frameworks successfully and others fail miserably. This article presents a popular and highly regarded psychology framework that will help you better understand how to implement Configuration Management.
Below are some observations I've made and I'd like to solicit the communities feedback on the conclusion I've drawn from it.
When looking at industrializing software development by creating a fully integrated and automated pipeline through which changes flow from check-in, through integration, build, testing, packaging and deployment; there are 2 paths one can follow:
1) Buy and implement a single vendor solution that covers the whole pipeline from check-in to deployment, the main drawback with this option being that most of the tools that make up the pipeline will do an OK job, not great, not the best in the industry but they will get the job done. Secondly there is the tie-in to a single vendor which is often perceived as a thorny issue because of the usual what-ifs and the constraints on customization of processes, tools etc.
Agile and ALM are two terms that you don’t often see side by side. To most developers, agile means team interaction, customer collaboration, dynamism, and responsiveness to change. In contrast, ALM seems to imply the opposite of agile, with echoes of rigid procedures, inflexibility, and top-down process control. But are the agile and ALM approaches as contradictory as they first appear to be?
“Expectations from IT just keep increasing every single day “– this is a point of view echoed by several CIOs across the organizations all over the globe. Newer developments in IT like Social Networking, Green IT, Virtualization, and Business analytics are changing the way businesses are run.
There are definite signs of Agile methods (with a capital A) may be losing mind share or, at the very least, suffering from a certain amount of perhaps over-hype or over familiarity. Or maybe it is just the rise in cases of AFS (Agile Fatigue Syndrome). For some, agile is giving away to the rise of lean software development. Where will it end?
Mario Moreira surveyed recently surveyed agile professionals to find out just how valuable CM processes and tools are to them. While there was a noticeable difference in opinion between different responder age groups, the overall response was overwhelmingly positive in CM's favor.