Skip to main content

Posts

Showing posts with the label Self-Organizing Teams

DevOps Leader

"Culture eats strategy for breakfast." Peter Drucker “Every company wants to behave like a software company.” Sanjay Mirchandani As the business environment continues to evolve and change, an adoption of a digital-first mindset is taking place in boardrooms across the globe. Today’s organizations face a never-ending torrent of change from the dynamics of global economics and competition, to the ever more rapid advancements in technology. These can be perceived as both an opportunity and a threat. The ability to adapt and innovate rapidly in this environment has become a core organizational competency. A leader is needed to bring about this change. Adoption of DevOps can bring about those needed changes that allow an organization to remain competitive in today’s market space. A successful DevOps transformation begins with a value stream map which can allow us to see a time diagnostic of our delivery lifecycle. This flow-based representation gives us an end to end

Agile Self-Organizing Teams

“Knowledge workers have to manage themselves. They have to have autonomy”, leadership guru Peter Drucker states in his   Management Challenges for the 21st Century . So what is a self-organizing team?   In many situations teams will be comprised of a group of people working together but not really dependent on what the others do to complete their individual tasks.   Teams should have four main qualities: Collaborative tasks to fulfill a  defined mission . Tying it to the overall vision, mission and strategy. Clear boundaries  in terms of information flow and alignment with other organizational teams, resources or decision-making policies. Roles, responsibilities and interfaces must to be defined. Authority to self-manage  within these boundaries. Must adhere to the overall organizational governance. Stability  over some defined period of time. Possibly defined in a project lifecycle or some other overarching documentation. In addition to these qualities, five essential

Agile Principles & ITIL

Underlying and supporting the  Agile Manifesto  are the twelve principles that help to bring the Agile philosophy to life. The DevOps movement encourages us to adopt and adapt these principles into the ITIL lifecycle not to reinvent it, but to allow us to make it spin faster.  Let’s take a look at them individually and interpret them from an ITIL, operational and support perspective. Our highest priority is to satisfy the customer.   We do this through early and continuous delivery of the proper utility & warranty. Welcome changes, even late in development, by using well defined and nimble change, release and deployment management, teams and models, allowing our customers to remain competitive in their given market spaces. Deliver updated working services frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. OK that one I modified a bit. We’ll   be Agile about it. Business people and IT must work together daily and collaborate