Enterprise development organizations are increasingly embracing agile as a concept, if not entirely in practice. That’s because adopting and scaling agile methodologies for large, complex enterprise software projects can seem daunting. Larry Ayres shares some tips for scaling agile development for enterprise software.
In his CM: The Next Generation Series, Joe Farah examines the following three steps that deal with process: defining the process, automating the process, and improving process quality. When a process is automated, problems can be repeated and are much easier to diagnose and correct. As the problems are corrected, we attain higher quality.
Small teams can have big dynamics that threaten the team’s success in terms of productivity and effectiveness. This article will examine some of the essential people issues that arise when implementing software configuration management (SCM) and application lifecycle management (ALM) with small teams.
There are many things to consider when picking an SCM standard or framework for your organization. Taking the time to explore compliance, politics, experience, and driving forces before making a selection will increase acceptance and smooth the transition.
Steve Berczuk is a regular contributor to TechWell and StickyMinds and a principal engineer and ScrumMaster at Fitbit in Boston. In this interview, Steve discusses configuration management and agile, helpful tools, and how testing has evolved over the years with the rise of agile.
This presentation covers conditions and expressions; truth tables; normal form patterns; modified condition/decision coverage; constructing an MC/DC test set; tools for checking MC/DC coverage; unique cause coverage; basic unique cause design; and logic coverage references.
All projects involve the three P's: people, process, and product. People includes everyone who influences the project. Process is the steps taken to produce and maintain software. Product is the final outcome of the project. To keep these three in harmony, you must observe who is trying to do what to deliver what. Usually, two of the three P's are mandated, and the third one is chosen appropriately. Although this is common sense, it is not common practice. Dwayne Phillips discusses the issues and challenges that affect us all on every project. Learn about the ideas and questions to consider to help you work through these issues.
Bill Buie presents a picture of what software configuration management looks like--and what it took to get there--in a real-life organization. Learn how one company built an infrastructure to support configuration management, including the tools and processes required. Lessons learned in deployment will be discussed, including identifying the right champions, incremental deployment, and the growth opportunity in tools.
There is an ever-growing need to provide complex software products to customers on a short development schedule. Additionally, the customers need to be able to count on release dates for planning purposes. Instead of investing in an entirely new tool set that solves the configuration management issues associated with supporting concurrent development and support, existing tools can be used. This paper focuses on how to adapt and in some cases enhance an existing set of well-known tools to enable Lucent to excel in the market place. To this end, this project chose to implement the Fixed Interval Feature Delivery (FIFD) model of software development.