Skip to main content

Half-hearted agile

Thought of penning down some of the issues I see with the projects where agile is tried via feeble mandate (lets just try it - top-down) rather than as a joint initiative between management and teams. The list will grow over time:

# communication
-->> Email being the preferred mode of communication rather than face to face communication
-->> Unwillingness to see the bigger picture by staying within the zone of "defined" responsibility
-->> Lack of communication on why we're doing it and how we want to do it
-->> Lack of training & coaching

# initiative
-->> Unwillingness to try something different
-->> Unwillingness to understand new ways of working
-->> This is how we work, this is common sense, this is the only way it is practical!
-->> We will not touch the Engineering practices

# openness
-->> Unwillingness to share progress, impediments
-->> View that Agile is just an "iterative" waterfall
-->> Buffer resources for some reason, not made visible to customer

# collaboration
-->> Handling the fixed price contracts with variable scope is difficult
-->> Will not start the work till the SOW is signed/cost & scope are cast in stone
-->> Someone needs to prove that Agile will not cost more than what we are used to

Comments

Popular posts from this blog

14 Essential Software Engineering Concepts for Engineers and Managers

There are many terms and concepts that are important for an engineer to be familiar with, in order to effectively build software. This post includes some of those terms. I will continually add to or update this list. Agile. A flexible and iterative approach to software development that emphasizes collaboration, customer feedback, and adaptive planning. My experience and success with agile development was the inspiration behind starting this blog. DevOps. A set of practices and tools that improve efficiency, speed, and reliability of the product through automation and optimization of the software development and delivery process where operational efficiency is part of the development process. Continuous Integration and Continuous Delivery/Deployment (CI/CD). A set of practices and tools that result in faster and more frequent releases, through automation of building, testing, and deployment of software. A key part of CI/CD is to deliver software to production frequently and using tec...

Forget Onboarding, do Alongboarding!

Alongboarding, an agile onboarding approach Alongboarding: We’re in it together! Organizations hire new people every day. A great first impression can make a tremendous difference in retaining employees. No one gets a second chance to make a great first impression, not even the best companies. An onboarding experience is an essential part of making that first impression on a new employee. Agile has been around for many years and has gained vast acceptance throughout the community. Yet, I find it disappointing that its tenets are not used well in most companies and most onboarding approaches follow a waterfall approach.  Alongboarding is an agile onboarding approach that applies agile tenets to onboarding new employees and makes the experience richer and more fulfilling. When I joined AppFolio as an agile coach, I experienced this approach during my onboarding. It felt like the team owned my success as much as I owned the team's success. It was a welcome change from some of m...

Make onboarding fun with Onboarding Canvas!

The Onboarding Canvas is a tool that can be used for onboarding a new team member . We derived this tool from Spotify's adaptation of the Toyota Kata . I like this tool because no one can tell you precisely how your onboarding should be like in order for you to be effective at your new job. This is a tool for continuous reflection and adaptation. It puts the newcomer in the driver’s seat, makes the onboarding process agile through continuous collaboration with your team. Four quadrants The onboarding canvas has four quadrants: Now: It defines where the team is now, what is going on and how is the new team member adapting to the change? Definition of awesome: With the addition of the new team member, how would the team like itself to be? What would be awesome for the new team member? Next target: In order to move towards "Definition of awesome" what outcomes should be achieved in the next x weeks? Next steps: What are the immediate next steps for the team...