Welcome!

Microservices Expo Authors: Liz McMillan, Elizabeth White, Charles Araujo, Ed Witkovic, Pat Romanski

Related Topics: Java IoT, Microservices Expo, Microsoft Cloud, Machine Learning

Java IoT: Book Review

The Scrum Field Guide: Practical Advice for Your First Year

Agile Software Development Series

This is one cool book. If you are starting to use Scrum, read it. If you are using Scrum, read it. If you are just wondering what Scrum is all about, read it. It gives the best insight into the workings of Scrum I have seen in a book.

The chapters are laid out in a really nice to read format. Each one contains sections titled The Story, The Model (or The Practices in some chapters), Keys to Success, References, and sometimes Works Consulted (although I never figured out what the difference between these and references where?).

The story is literally a story that comes from the author's field experience that introduces the topic the chapter covers and brings to light problems being solved by the next section, The Model.

The Model and the Practices sections are the guidance and suggestions to help with the problems identified in the story. Keys to Success provide advice on how to execute the model.

The book starts with an introductory chapter, Scrum: Simple, Not Easy, in which the author makes some very important points. I don't know how many times I have repeated the sentence, "Agile does not mean easy and I believe it requires much more experience to pull off than traditional processes".

The book is then broken down into four parts. I have listed the parts and the chapters below.

Part I- Getting Prepared
Getting People On Board
Using Team Consultants to Optimize Team Performance
Determining Team Velocity
Implementing the Scrum Roles
Determining Sprint Length
How Do We Know When We Are Done?
The Case for a Full-Time ScrumMaster

Part II- Field Basics
Why Engineering Practices Are Important in Scrum
Core Hours
Release Planning
Decomposing Stories and Tasks
Keeping Defects in Check
Sustained Engineering and Scrum
The Sprint Review
Retrospectives

Part III- First Aid
Running a Productive Daily Standup Meeting
The Fourth Question in Scrum
Keeping People Engaged with Pair Programming
Adding New Team Members
When Cultures Collide
Sprint Emergency Procedures

Part IV- Advanced Survival Techniques
Sustainable Pace
Delivering Working Software
Optimizing and Measuring Value
Up-Front Project Costing
Documentation in Scrum Projects
Outsourcing and Offshoring
Prioritizing and Estimating Large Backlogs
Writing Contracts

Appendix- Scrum Framework
The Roles
The Artifacts
The Meetings
Putting It All Together

Every chapter was great, but I really liked Documentation in Scrum Projects, Using Team Consultants to Optimize Team Performance, The Fourth Question in Scrum, and Outsourcing and Offshoring. All these chapters contain topics I usually see Scrum teams avoiding.

A lot of agile teams like using the agile process as an excuse for not doing documentation. The author makes it very clear that documentation can rarely be dismissed. It is about doing what is needed to succeed, and planning and documentation are tools for success when they aren't over done. Too much can kill your project just as easily as doing none.

The Fourth Question in Scrum rocks. This basically brings to the table all chatter that happens after the daily standup when a project is hitting rocky ground. It gives the team a chance to voice their real opinion of how things are going.

The author provides a very realistic picture of what outsourcing and offshoring actually cost and how much hidden extra effort is involved.

The team consultant model does a good job of showing how to structure a flexible team structure.

One thing I would have liked to see more of is the inclusion of the actual practices that are executed in order to produce the documentation the author mentions. An example is architecture. The architecture documentation that results from the architecture definition process (or the Architecture Business Cycle) is just an artifact of many practices that need to be preformed throughout the entire project.

The author also includes a link to supplemental material which includes some nice tools. I really like the 14 and 30 Day Sprint Backlog Templates.

Over all I thought this book was great. It pulled a ton of real project experience into one place. It was also an easy read. The author's writing style made it really easy read. The stories were all interesting and were a cool way to lead into the chapter's topics.

The Scrum Field Guide: Practical Advice for Your First Year

More Stories By Tad Anderson

Tad Anderson has been doing Software Architecture for 18 years and Enterprise Architecture for the past few.

@MicroservicesExpo Stories
In his keynote at 19th Cloud Expo, Sheng Liang, co-founder and CEO of Rancher Labs, discussed the technological advances and new business opportunities created by the rapid adoption of containers. With the success of Amazon Web Services (AWS) and various open source technologies used to build private clouds, cloud computing has become an essential component of IT strategy. However, users continue to face challenges in implementing clouds, as older technologies evolve and newer ones like Docker c...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
"This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The purpose of this article is draw attention to key SaaS services that are commonly overlooked during contact signing that are essential to ensuring they meet the expectations and requirements of the organization and provide guidance and recommendations for process and controls necessary for achieving quality SaaS contractual agreements.
What's the role of an IT self-service portal when you get to continuous delivery and Infrastructure as Code? This general session showed how to create the continuous delivery culture and eight accelerators for leading the change. Don Demcsak is a DevOps and Cloud Native Modernization Principal for Dell EMC based out of New Jersey. He is a former, long time, Microsoft Most Valuable Professional, specializing in building and architecting Application Delivery Pipelines for hybrid legacy, and cloud ...
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
CloudEXPO New York 2018, colocated with DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.
Docker is sweeping across startups and enterprises alike, changing the way we build and ship applications. It's the most prominent and widely known software container platform, and it's particularly useful for eliminating common challenges when collaborating on code (like the "it works on my machine" phenomenon that most devs know all too well). With Docker, you can run and manage apps side-by-side - in isolated containers - resulting in better compute density. It's something that many developer...
In his keynote at 19th Cloud Expo, Sheng Liang, co-founder and CEO of Rancher Labs, discussed the technological advances and new business opportunities created by the rapid adoption of containers. With the success of Amazon Web Services (AWS) and various open source technologies used to build private clouds, cloud computing has become an essential component of IT strategy. However, users continue to face challenges in implementing clouds, as older technologies evolve and newer ones like Docker c...
"We're developing a software that is based on the cloud environment and we are providing those services to corporations and the general public," explained Seungmin Kim, CEO/CTO of SM Systems Inc., in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual ...
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at @ThingsExpo, James Kirkland, Red Hat's Chief Archi...
Containers and Kubernetes allow for code portability across on-premise VMs, bare metal, or multiple cloud provider environments. Yet, despite this portability promise, developers may include configuration and application definitions that constrain or even eliminate application portability. In this session we'll describe best practices for "configuration as code" in a Kubernetes environment. We will demonstrate how a properly constructed containerized app can be deployed to both Amazon and Azure ...
We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual ...
We all know that end users experience the Internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices – not doing so will be a path to eventual b...
Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
The past few years have brought a sea change in the way applications are architected, developed, and consumed—increasing both the complexity of testing and the business impact of software failures. How can software testing professionals keep pace with modern application delivery, given the trends that impact both architectures (cloud, microservices, and APIs) and processes (DevOps, agile, and continuous delivery)? This is where continuous testing comes in. D
JetBlue Airways uses virtual environments to reduce software development costs, centralize performance testing, and create a climate for continuous integration and real-time monitoring of mobile applications. The next BriefingsDirect Voice of the Customer performance engineering case study discussion examines how JetBlue Airways in New York uses virtual environments to reduce software development costs, centralize performance testing, and create a climate for continuous integration and real-tim...