Like many IT organizations in state government agencies, this New York State Government Agency primarily used Waterfall. I implemented the agency’s first agile projects. I was challenged by the agency’s unique environment, learned lessons, discovered systemic problems, overcame organizational obstacles and changed misconceptions. I will discuss what I’ve learned during this award-winning project and make recommendations for others in bureaucratic companies and government agencies. The agency’s projects are moving to agile/scrum and the institution’s IT group is incorporating agile into its PM and SDLC methodologies.
Implementing Scrum is difficult and it is always difficult to answer the question of where to start this Agile Travel. In this article, Ilan Goldstein shares 10 tried-and-tested steps to help new practitioners get their Scrum show on the road.
Implementing Scrum is difficult and there might be nothing better than taking time and making mistakes to adopt Agile successfully. This being said ” Scrum Shortcuts without Cutting Corners” is a book that can help you to choose better trails when you explore some of the Scrum practices.
As Rex Lester explains in this article: “Implementing Scrum involves adoption of a new paradigm across the organization. In most instances, the severe level of culture shift and change aren’t really appreciated”. The article discusses the difficulties of moving an organization from a Waterfall process to an Agile approach.
Adopting an Agile approach in a software development organization requires more than just sending some people to a Certified ScrumMaster (CSM) course. In this article, John Hill provides six recommendations for an enterprise Scrum transformation.
It would be so easy if everyone at our companies just used Scrum or at least Agile. No one would lean on the team for dates and deadlines, and everyone would know that change is a good thing. It’d be one great big happy project management family. But let’s face it: an all-Agile organization isn’t always possible.
There is a tendency to use agile software development approaches and all their practices simply because it is in the book. Why don’t we select the tools based on the context of the task we are trying to complete?