Objective Thoughts

Subscribe to our blog Net Objectives Thoughts Blog

Addendum to How to Abandon Practices

May 19, 2015 — Posted by Al Shalloway

In our Day 3 of SAFeTM: Elaborating SAFeTM, the fourth webinar on Leanban, I discussed how to abandon practices.

Here were a couple of other tables of interest.  This relates to my earlier blog How to Abandon Practices.

Focus on Outcomes, Not Practices

Share this:


Abstractions Save Testing Time in TDD

April 27, 2015 — Posted by Ken Pugh

In my Prefactoring book, I have a guideline “When You’re Abstract, Be Abstract All the Way”. The guideline recommends never using a primitive (e.g. int or double) in a parameter list, except as a parameter to a constructor. Although the book was primarily focused on creating high quality code in general and not specifically on test-driven development (TDD) , it turns out this guideline can help save time in TDD by aiding in reducing redundant tests.

Share this:


SAFe's Answers to Our Inflection Points

April 14, 2015 — Posted by Al Shalloway

Early last year I wrote a blog that described what you must address at Scale - Not Doing SAFe®? No Problem. Not Doing These? Big Problem.

Share this:


What Every Framework/Method Should Have

March 28, 2015 — Posted by Al Shalloway

I was asked my thoughts about the blog LeSS SAFeTM.Comparison. It prompted me to think - many people are comparing one approach to another.  I've done this myself as I think it's a way to learn options that are available. But most folks don't go far enough. Instead of asking "how does A compare to B?" perhaps we should be asking "what does A and B need?"  

Share this:


Inflection Points in Software Development

March 10, 2015 — Posted by Al Shalloway

At Net Objectives, we’ve been doing Agile at the team level for over 16 years and Agile at small scale (25-150) to large scale (1000 on up) for over a decade.  It is surprising how relatively few things must be identified and managed to do this well.  It’s also interesting that many of the large scale items must be managed at small scale as well.  For example, how teams work together must be managed at all degrees of scaled agile.  That it must be managed is one thing, how this issue is managed is something else and depends significantly on where the organization is (current culture, proce

Share this:



Blog Authors

Al Shalloway
Business, Operations, Process, Sales, Agile Design and Patterns, Personal Development, Agile, Lean, SAFe, Kanban, Kanban Method, Scrum, Scrumban, XP
Cory Foy
Change Management, Innovation Games, Team Agility, Transitioning to Agile
Guy Beaver
Business and Strategy Development, Executive Management, Change Management, Lean Implementation, Transitioning to Agile, Lean-Agile, SAFe
Israel Gat
Business and Strategy Development, DevOps, Lean Implementation, Agile, Lean, Kanban, Scrum
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, SAFe, Kanban
Ken Pugh
Software Design, Design Patterns, Technical Writing, TDD, ATDD, Coaching, Mentoring, Professional Development, Agile, Lean-Agile, Lean, SAFe, Kanban, Kanban Method, Scrum, Scrumban, XP
Marc Danziger
Business and Strategy Development, Change Management, Team Agility, Online Communities, Promotional Initiatives, Sales and Marketing Collateral
Scott Bain
Analysis and Design Methods, Agile Design and Patterns, Software Design, Design Patterns, Technical Writing, TDD, Coaching, Mentoring, Online Training, Professional Development, Agile
Tom Grant
DevOps, Analyst, Analysis and Design Methods, Innovation Games, Lean Implementation, Lean-Agile