![]() The success of the cloud model – both the public cloud and the offshore delivery “cloud” – has proven beyond doubt that work will increasingly be done in partnership with others. Work, though, is beyond the walled garden of companies. And that clean canvas thinking required creating a parallel universe of channels, one for every “boring” work item recorded by legacy systems of record. Of course, they had to shun all metadata – process, product, customer object models – to achieve their “work os” moniker. Even machines could participate via their bots! That’s how egalitarian social could be. From emojis and reactions to grassroots channels and search, the social tool had made collaboration real-time, delightful, and mobile. Slack was a master of all things informal. The informalism of GitHub Issues and Slack was very attractive to companies craving for end user feedback, product-market fit (PMF) jitters, and in-app-everything. In the last decade, as B2B went SaaS, startups started to care about informal work and real-time collaboration, including with end users and partners. Users, no one bothered! After all, “users” were a B2C jargon, so why should a B2B software company care? Customers were the domain of CRM systems. Product was relegated to component dropdowns at best. More importantly, it celebrated process, and process alone. Jira had uncontrolled metadata, one KPI too many, and way more administration than what makers could fathom. Work needed to be more than a chore, a mere statistic. The uncontrolled sprawl of metadata made developers crave for a system of engagement that was less informal, more delightful. Systems of record were now the breeding ground for vanity metrics such as developer productivity, story points, and burndown charts. Tickets became the new waterfall, and developers became loath to update them, while managers worried about the accuracy of their dashboards. Work became continuous and even more bite-sized, powered by informal chats and social conversations. Process was king.Īgile morphed into continuous integration and continuous deployment with the advent of cloud. Companies went from monolithic waterfall release planning to agile development methodologies with sprints, epics, and stories. ![]() Over the years, Jira went from being a bug tracking tool to a platform for workflows and product management. Startups went from spreadsheets and emails to a system of record that helped scale their businesses. Engineering organizations went from expensive desktop tools to an affordable lightweight web application that upgraded often. Jira not only changed how we built software, but also how software companies worked. Atlassian, the company behind Jira, was an original PLG company that let developers use its freemium software, no questions asked. The magical ticket management system fueled an era that was increasingly powered by the web browser, open source, and offshore development. ![]() Almost 20 years ago, Jira redefined work for developers.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |