The IT industry is dominated by men. But you shouldn't hire more women just to lessen the gender gap. The ultimate goal is better teams, and it just so happens that hiring more women tends to help build better teams anyway. Companies should reexamine what traits they value in job candidates.
Kristin Cowhey explains how z/OS development has evolved throughout the years and what that means for developers and tech personnel. With legacy developers leaving the workforce, there’s a dire need to replace the knowledge in order to maintain the mainframe systems and applications that are still in use today.
There is a lot of hard work and recalibration needed to adopt an agile approach. Just as one does not simply walk into Mordor, you also cannot simply decide to be agile. In this article, Alison Jacques describes her IT department’s experience transforming to agile and shares some of the lessons learned and tools she’s adopted to ensure continued success.
Kent McDonald introduces us to Arthur, a middle manager and product owner in a medium-sized insurance company who has been assigned to take on an agile project. For those unfamiliar with agile, the terminology and techniques of agile approaches can seem strange and often a little silly when not accompanied with an explanation as to why those techniques exist. Kent explains the challenges product owners like Arthur face and how to make product owners understand agile better.
By emphasizing better communication and collaboration between software development and IT, this article explores ways to establish trust by focusing on customer value. For example, Manoj Khanna suggests continuous integration and validation as techniques that helps build that trust.
For years we've all heard how software development and IT are a mixture of art and science. As our industry matures and becomes more mainstream, Johanna wants to upset the apple cart by suggesting that there's a missing and sorely needed ingredient—professionalism.
As organizations grow and diversify, they end up with a large number of IT systems. However, by quantifying sustainability metrics, they can optimize their IT infrastructures and introduce a greener side of IT.
For development, a production application should be fully baked and not in what would be considered a “development” state. Tracy Ragan explains that frequent releases are a basic requirement of rapid development methodologies like agile and this impacts the way in which development teams and production control teams must interact.
Joe Townsend has been working in the configuration management field for fifteen years and is a regular contributor to CMCrossroads. In this interview, Joe discusses how configuration management has changed over the years, the trouble with tools, and trends in IT.
Dr. Dobbs senior contributing editor Scott Ambler sits down with Noel Wurst at Techwell.com to discuss how agile team governance does not have to have a negative stigma. Scott helps people see through naive assumptions, while eliminating out of control governance to get teams back on track.
Establishing IT governance and compliance practices is essential for organizations that have regulatory or audit requirements. The good news is that you can be agile and still comply with Sarbanes-Oxley, CFR 21, HIPAA, and other regulatory imperatives. Done well, IT controls actually help you improve both productivity and quality. Bob Aiello describes how to implement IT controls in frameworks such as ISACA Cobit and ITIL v3 that many regulatory frameworks require-while maintaining agile practices. Bob's guidance includes specific examples of establishing IT controls: separation of duties, work-item to change-set traceability, physical and functional configuration audits, and more. Bob explains how these practices help government, defense, and corporations scale agile practices where audit and regulatory compliance is a must.
Developers and testers are under constant pressure to operate more efficiently, cut costs, and deliver on time. Without access to scalable, flexible, and cost effective computing resources, these challenges are magnified. Brett Goodwin explains how to create scalable dev/test environments in the cloud, and shares best practices for reducing cycle time and decreasing project costs. Learn how scalable, cloud-based data centers can run software without complicated re-writes; enable rapid defect resolution with snapshots and clones; and provide global collaboration for multiple product and release teams. Brett presents a case study of Cushman and Wakefield, the world's largest privately held real estate services firm, which struggled with an on-premises development and testing environment.
The role of the software tester is continuing to evolve, becoming more complex and more technical. As new methodologies, technologies, and platforms emerge, testers are bombarded with new, so-called "best practices" on how to do their jobs. The problem is that testers have heard the same songs with different lyrics for more than twenty years now. Clint Sprauve takes a contrarian’s view of testing and the quality assurance industry. He examines some of today’s typical testing "best practices"-keyword-driven testing, requirements traceability, the tester’s role in agile development, quality reporting, tool expertise, and quality certification programs-while providing alternative approaches for how to view each practice.