The more we meet software development organizations, the more we see how Jira, the most popular ALM tool out there, is being misused. Abusing the tool is quite easy actually… Paraphrasing Tolstoy’s words from Anna Karenina, “Good Jira implementations are all alike but unhappy implementations are all unhappy in their own way”. (In AgileSparks we keep a warm place for the classics). We have seen many cases where the abuse of the tool caused frustrations and inconsistencies with the Agile mindset that put at risk the ability to benefit from Agile practices adopted by the organization.
The subject of my talk today was “Introduction to Lean/Agile scaling approaches” where talked about why scaling approaches are necessary and when to actually try to de-scale as well as gave a very brief introduction to a couple of the key frameworks we typically use – SAFe, Large Scale Scrum, Spotify’s approach, Connected kanbans. I then finished with some decision criteria questions to ask yourself as you’re starting this journey.
How to use:
Gather your team
Go through the scan and score what you are doing and what not.
Figure out what you want to try next that will improve your capabilities in the relevant direction.
Continuous deployment is a process that encourages developers to push new code to production whenever they can. In this presentation, Itai will explain the principles of continuous deployment and will show how Outbrain can deploy code more than 20 times a day while serving recommendations to top publishers (including USA Today, iVillage, Boston.com, Chicago Tribune, Newsweek, TheStreet, The Boston Globe, and Slate. Hebrew: Ynet, Haaretz, TheMarker, Globes, City mouse, JPost and more).
Over the past couple of years, my colleagues and I have led dozens of implementations in a variety of companies. As we closed the second year of our company we began noticing the problems and costs incurred by the fact that we each worked differently. E.g. miscommunications, differences in outcomes, and rework done between implementations. We decided it was time we go and analyze our past implementations for common goals and methods of operation.
I will be talking about:
* The problems that we wanted to solve (some are still with us) and how the Kanban mindset helped us define the change and then implement it
* what challenges we encountered along the way
* what’s important (in my opinion) in this process
* what did we gain (so far) from implementing the change at Pelephone
Going Agile via the Fast Lane – How FiftyOne.com switched from quarterly releases to 2 weeks Scrum and Kanban.
Ben Peer shares the story of FiftyOne.com’s transition in the last year. Starting with Scrum, involving the whole team in true inspect and adapt, evolving to Kanban/ScrumBan, evolving team formation and definition of done, adding Agile Testing approaches including ATDD. In parallel, tight collaboration with a remote Product Management team, and usage of an electronic highly visual Kanban board. Ben will discuss the benefits, the challenges and how the team dealt with them, and will provide recommendations to others considering this journey.
Request for additional information and prices