Agile Application Development Infrastructure Software Development 
Leading Agile
APRIL 24, 2019
Tech Infrastructure != This is a slightly broader definition of “front-end” that we normally hear from, say, web app developers. I’m including all IT resources “in front of” the API layer in the organization’s technical infrastructure. Half-Agile Transformations. Value Stream.
Leading Agile
JUNE 8, 2018
We did the application development work in Part 3. Now you’ll become an infrastructure engineer. Similarly, if you’re coming from an infrastructure background, then I hope the section of the exercise that involved test-driven development was informative. You became a programmer in Part 3. Well, sort of.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Leading Agile
OCTOBER 31, 2018
The project is a set of scripts for provisioning and configuring a lightweight software development environment based on Ubuntu Server , a Linux operating system distribution. System administrators and infrastructure engineers don’t always use shell languages. Rspec home page (ChefSpec is based on Rspec). ChefSpec Example.
Herding Cats
JANUARY 20, 2018
But in the software development world, the domains of IT, there are two other colors of money. There are two types of software that are developed for a business: 1) internal-use software, and 2) software developed to be sold, leased or marketed (“software to be sold”). CAPEX and OPEX.
MPUG
OCTOBER 9, 2019
Please find below a transcription of the audio portion of Tim Runcie’s Agile Series Part 1 webinar being provided by MPUG for the convenience of our members. Kyle: Hello everyone and welcome to today’s MPUG training series, part one, Understanding and Incorporating Agile Project Management. It’s not all or nothing.
Leading Agile
FEBRUARY 11, 2019
When I first learned about Agile methods in 2002, the principles seemed to offer an ideal solution to many organizational issues common at the time. It’s time now to move forward to the next level of proficiency in software delivery; what we might call “post-Agile.” Stable Team. Dedicated Team. Team Spaces.
Leading Agile
OCTOBER 22, 2018
In the 1960s, it was considered a baseline good practice in software engineering to test your code as you wrote it. The pioneers of software development in that era were proponents of various levels of testing; some advocated “unit” testing and some didn’t, but all recognized the importance of testing code.
Expert insights. Personalized for you.
118 
Let's personalize your content