Objective Thoughts

What It Takes to Do Large Scale Technical Agile

October 14, 2013 — Posted by Al Shalloway

Agile requires attention to quality code.  While teams may get away with deferring technical Agile practices in business applications and IT, there is no such luck in technically oriented applications such as virtual machines, compiler writing or real-time networking applications.  When multiple teams are involved in building technical products the challenges become even greater.

Click here for the rest of this article.


Share this:




  

SAFe Kanban

September 29, 2013 — Posted by Al Shalloway

When people ask “can Kanban be done under SAFe at the team level?” they are typically referring to Kanban practices.  The starting point to answering this question, however, must be to look at the mindset underneath these approaches.  This is a bit more complicated, but provides more power because mindsets create the context for practices 

What is Kanban?

Before proceeding, however, we must be clear what we mean by ‘Kanban’.   Kanban is an overloaded term meaning three distinct things:


Share this:




  

Re-Defining the Possible

September 8, 2013 — Posted by Scott Bain

Note from Al Shalloway.

This blog was written by Scott Bain, one of our instructors. However, it's a strong statement from all of us. Our combined experience of more than a century and a half bears out Scott's well-crafted message ushering in a new paradigm for design.

Re-Defining the Possible

Scott L. Bain, Net Objectives


Share this:




  

Why You Should Be Concerned When a Consultant Says "That's Orthogonal"

August 31, 2013 — Posted by Al Shalloway

I have heard several proponents of popular frameworks and methods excuse the lack of some key concept as "well that's orthogonal to the framework/method, but we expect you to put it in if you think it has value." In this case the word "orthogonal" means independent or de-coupled from the framework/method in question.  The challenge with this is threefold:


Share this:




  

A Tale of Two Kanbans… or Three

August 26, 2013 — Posted by Al Shalloway

Kanban is a widely used method for process management, scheduling, and transition management with deep roots in Lean. As early as 2007, a group of software developers – David Anderson, Jim Benson, Corey Ladas, Darren Davis, and others – applied kanban to the process of software development, calling it Kanban for Software Engineering.


Share this:




  

Pages

Free Email Updates!

Sign up for free email updates from
Net Objectives Thoughts Blog

Blog Authors

Al Shalloway
Business, Operations, Process, Sales, Agile Design and Patterns, Personal Development, Agile, Lean-Agile, Kanban, Scrum, Scrumban, XP
Cory Foy
Change Management, Innovation Games, Team Agility, Transitioning to Agile
Jim Trott
Business and Strategy Development, Analysis and Design Methods, Change Management, Knowledge Management, Lean Implementation, Team Agility, Transitioning to Agile, Workflow, Technical Writing, Certifications, Coaching, Mentoring, Online Training, Professional Development, Agile, Lean-Agile, Kanban
Ken Pugh
Software Design, Design Patterns, Technical Writing, TDD, ATDD, Coaching, Mentoring, Professional Development, Agile, Lean-Agile, Scrum
Scott Bain
Analysis and Design Methods, Agile Design and Patterns, Software Design, Design Patterns, Technical Writing, TDD, Coaching, Mentoring, Online Training, Professional Development, Agile