“If you don’t like my solution, you don’t care about fixing the problem.” ... When time and money is spent fixing the symptoms and not the problem itself, the symptoms are often confused with the problem.
As the world is becoming more dependent on global partners, teams are joining forces with employees from around the world. To keep pace with the rapidly changing industry, companies are utilizing management strategies like Scrum, DevOps, and DevSecOps to increase productivity and communication. This left many remote teams in the dark... until now. Meet the new “distributed scrum team.”
I just finished rereading Scrum: The Art of Doing Twice the Work in Half the Time, by Jeff Sutherland. When I finished, I suggested the book to both my son James and my apprentice at Sustainable Evolution, Andrew Wilt. They both LOVED it. Andrew was enthused enough to suggest we start running weekly sprints and daily standups. In the coming weeks, I will write a book review and he will add his thought in a Scrum blog piece. I’m sure we will have follow-up posts as we move forward with this pilot and adopt this approach to working together. Since Andrew lives in one state and me in another, we will have to use technology to close the gaps.
Service-oriented architecture (SOA) is now a teen. In the early 2000s, SOA was just becoming the leading-edge discussion point for architects. Now that SOA has passed its awkward, gangly stage and is fully into its informative teen years, maturing nicely. And, just like any teen, SOA is developing its own language and approach. As I speak to people, some get confused with the use of the new terms.
As you may (or may not) have read, I am (still) involved in the local (Seattle) chapter of Iasa first ever IT architecture competition. Team Skyscraper has delivered their second set of deliverables and are now in the home stretch. With the business requirements and conceptual architecture being the first set of deliverables, this past weekend they had to submit software, infrastructure and security architectures, and the technology stack they chose.
One of my favorite things I get to do at SEI is write weekly blog posts to engage with the public and our community. This was my first year writing in this format and I have learned a lot along the way. One year and 37 posts later (plus 32 posts by SEI mentor, Andy Ruth), 2015 has taught me 11 mandatory lessons every blogger should consider:
As you may (or may not) have read, I am involved in the local (Seattle) chapter of Iasa first ever IT architecture competition. We are at the point where the rubber meets the road. Team Skyscraper needs to submit their first set of deliverables this weekend on the 22nd. The deliverables are a business requirements document and initial draft of an architectural design document with conceptual and information architecture complete.
Stories began as campfire tales and paintings on cave walls. They were stories of practical information; where to hunt and gather food; stories of thankfulness to gods; stories of nature and fear. The art and business of story has been with us since the beginning of recorded history and remains to as an integral thread in the fabric of our lives.
A dear friend of mine, Leslie Goh, sent me a link to a piece in the New York Times. She suggested it reminded her of me. The piece, written by David Brooks, suggests the need for two bucket lists. Brooks, who is successful from a business sense, talks about meeting others who seemed to be successful in a way he was not. This led him to think about a different bucket list not tied to business goals or personal goals, but rather moral or virtuous goals. The way he organized these different groupings is into resume virtues and eulogy virtues.
Are you still waiting for your personal jetpack or flying car? In 2011, I read a fun ZDNet blog piece about the future of information technology. Well, at the time it really wasn’t much predicting as it was documenting trends. But let’s take a look at then and now, and look at 5 to 10 years in the future, what that might look like and how it might impact your career.
There was a recent article in the New York Times that painted a pretty bleak picture of working at Amazon, followed by a ton of responses for and against what the article stated. Over the years, I have read quite a few of those articles and now that I am Seattle-based, I work in a high-tech company area. For what the article said, you could change the name of the high-tech company and reprint. So the question isn’t this high-tech company or that one, rather, it is high-tech company or not high-tech company.
Yesterday, I had the pleasure of working with a team that focused on chasing and being chased, and trying to limit the amount both team members have to do. In business, you rely on other people to provide you something so you can do your job, and others rely on you to provide something to somebody else so they can finish their job. Hence, chasing and being chased.
Many people in the workforce are disenfranchised with the company they work for and have limited loyalty to the company. There are several factors surfacing this feeling in current and new workforce entrants. Holacracy is a different approach to running a company that removes structure and distributes authority and responsibility.
Boy, I LOVE a good marketing effort to advance ideas forward. DevOps is IT’s approach to applying Lean best practices to SOA and the practice of putting IT capability in place. The Internet of Things (IoT) is pretty similar in that it is reusing an existing idea. We now have discreet (and smart) devices available to most everyone that are connected to the Internet so we can pull data into a server, manipulate it, and take action against that information.
This is no longer your mother’s coding space. Over the last 10 years and specifically in the last 4-5 years the practice of coding/developing applications, solutions, and products has flipped over in a pretty big way. Disruptive is the word that comes to mind, and in my opinion, disruption is where innovation lives. So what does the leading edge of the coding world look like?