This is the last post in this series on the ways that IT teams work. I complete this series by examining the characteristics of teams that make them effective regardless of the way they are organized to carry out their work.
Read More
Posted: January 9, 2017 |
This is part three of a series on how teams are organized and how they work together within this set of conventions and constraints. This post describes a team that creates software with members that work on multiple line items on the same projects within a fixed time period. It can be described as a group in a box unified by schedule.
Read More
Posted: January 2, 2017 |
This is part two of a multi-part series on how teams are organized and how they work together within a set of conventions and constraints. This post describes an organization that creates products and offerings with members that work simultaneously on multiple projects. A well-defined process, not very different from a traditional systems development life cycle (SDLC), guides this federated team.
Read More
Posted: December 19, 2016 |
This week, I’m starting a multi-part series on how teams are organized and how they work together within a set of conventions and constraints. I am writing this series from my own experience as a team member at different parts of my career.
Read More
Posted: December 12, 2016 |
This week, I’m continuing the series on significance (the quality of being worthy of attention or importance). For this post, I want to focus on the well-formed and innovative ways that humans manage enterprise systems, network and applications. I will also survey the notion of a comprehensive list of all services provided by IT, an inventory of enterprise capabilities.
Read More
Posted: December 5, 2016 |
This week, I’m continuing the series on significance (the quality of being worthy of attention or importance). For this post, I want to focus on a remarkable z/OS utility called System Modification Program/Extended (SMP/E).
Read More
Posted: November 28, 2016 |
This week, I am continuing this series on significance (the quality of being worthy of attention or importance). For this post, I want to focus on a component of z/OS called Workload Manager (WLM). It handles the varied and diverse work that runs in a z/OS system giving the individual jobs, started tasks and time sharing option (TSO) users the system priority desired by the business that’s running the software.
Read More
Posted: November 21, 2016 |
This week, I am continuing this series on significance (the quality of being worthy of attention or importance). For this post, I want to focus on a component of z/OS called SMF. As a new application developer, I had no exposure to SMF. It was something developers didn’t know about because we were focused on other things like using COBOL and VSAM to code a solution to the specs given to us by our analyst. Later, when I became a system programmer trainee, I became aware of the enormous significance of SMF.
Read More
Posted: November 14, 2016 |
Last week, I wrote about how middleware came about because of the emergence of distributed computing systems. I wrote that these new systems created a need for certain types of software that had not existed before or existed mainly for internal use. Middleware software has roots in software that was developed for centralized computing for both batch and online processing. This week I focus on the real-time roots of modern middleware.
Read More
Posted: November 7, 2016 |
It’s generally accepted that modern middleware came about because of the emergence of distributed computing systems. These new systems created a need for certain types of software that hadn’t existed before or existed mainly for internal use. This new software came about to support client-server computing. However, modern middleware software has firm roots in software that was developed for centralized computing.
Read More
Posted: October 31, 2016 |
