CodeStringers resources

Agile Software Development Resource Center

Scrum.org, the Scrum Alliance, Mountain Goat Software,… they make it sound easy. However, “tuning” the Scrum method to deliver great software takes years of experience and lots of mistake along the way.

If you’d like to stay informed on our Agile Insights, enter your email and we’ll remind you every time we have an update.

white papers

Agile Software Development Resources.

White paper

Introduction to Agile Development.

Mastering agile and the Scrum Methodology within your development organization is likely to require some trial and error as no two organizations apply the method the same way.

Read this Paper

White paper

Scrum Methodology Fundamentals.

An overview of the Scrum development methodology manifesto, framework, roles, ceremonies and artifacts.

Read this Paper

White paper

Agile vs Waterfall.

In this section of the Agile Software Development Resource Center, we provide an overview of Scrum vs Waterfall, because those methodologies are virtually opposites of one another in terms of guiding principles, execution and outcomes.

Read this Paper

White paper

Writing Effective User Stories.

The ability to write agile software requirements – user stories – is perhaps the most critical skill needed to maximize development velocity. User stories that are too large, vague, or lack a clear definition of done all result in confusion by the Scrum team. And confusion means wasting valuable time during development Sprints gaining clarity rather than doing their jobs.

Read this Paper

White paper

Estimating in Story Points.

An explanation of story points, velocity, and how to estimate user stories quickly, accurately and without the unnecessary pressure that time-based estimates put upon the development team.

Read this Paper

6-Software-Release-Planning-–-An-Overlay-to-Scrum.webp

White paper

Release Planning in Scrum.

Few (actually, no) software product is built in a single development Sprint. Yet, the Scrum method’s largest increment is one sprint. Adding software release planning and management either requires a different method or some creativity in overlaying release planning atop the Scrum Methodology.

Read this Paper

About the Author

Michael Manzo

President & CEO

Home

I’ve been working in software development for 25 years and have either worked in or managed most job functions for various software development firms. I began my career as a Product Manager. My passion is understanding users and their needs, and innovating to address those needs.

Until 2012, I worked for a variety of venture-funded telecom software firms, ranging from telecom vendors to B2B and B2C companies.

My first introduction to agile software development and the Scrum methodology was my role just prior to CodeStringers. So all told, I have 15 years of experience in agile software development.

But reality is that my real experience – in which I learned the lessons one only learns by “doing” has come since joining CodeStringers in 2012. Since then and primarily because CodeStringers provides custom software development services (in addition to building our own products), I’ve had the opportunity to oversee the definition, development and maintenance of dozens of software products for clients ranging from startups to large enterprises.

That experience has afforded me quite a bit of development methodology wisdom. Earlier on in this experience, I created an “agile primer” presentation that I shared with clients to help their teams better understand and apply the agile method. And on this page, I’ll share what I’ve learned.