Almost a decade has passed since Marc Andreessen’s article “Why Software Is Eating The World” passionately defended the rise of software and its potential to disrupt every industry. The ensuing decade has proven his thesis to be true. With additional machine learning tools embedded in software, we are just scratching the surface of what software will offer in the decade to come.
Software and software developers do not live in a vacuum but work within teams enabled by tools to reach product objectives. How those products get built is an important consideration when defining your future product plans to achieve great results for your customers and your organization. Build management is one of many key category tools within the software development lifecycle (SDLC). In fact, over the previous two years source code collaboration tools like GitHub have become one of the top three tools used by software developers.
On April 14, 2020, GitHub made an important announcement about removing the paywall for GitHub team features. Now development teams can use the popular source control collaboration tool with unlimited private repositories and an unlimited number of collaborators. However, those who wish to subscribe to more advanced features such as code ownership, SAML, and personalized support can opt for paid plans.
Source: SoftwareReviews Product Scorecard, Accessed April 24, 2020.
When the industry lowers barriers to entry, innovation and entrepreneurship increases and software advances at a rapid pace benefiting us all. GitHub was already a very popular and important tool for development teams. Releasing its core features free to all will benefit development teams so they have the best tools to complement their software delivery practices.
So you’ve gone Agile. You do daily scrums, retrospectives, and all the “right” Agile ceremonies. But still your organization isn’t quite convinced. It is now critical to balance the drivers and goals of both Agile and traditional thinking in order to achieve organizational success.
Do you feel like your Agile teams are treading water – going through the motions but never going anywhere? It’s a risk, and practices such as daily standups, retrospectives, and demonstrations need to be used wisely or you risk losing discipline to meeting fatigue.
Stakeholders expect the speed and responsiveness of product delivery does not come at the expense of quality. QA tools offer retailers the ability to continuously ensure both business and technical quality standards are upheld, but these tools should not be viewed as a silver bullet.
When trying to implement Agile as a defined process, Scrum turned BAs or other roles into order takers with the title “product owner.” This undermines the entire value proposition of product management.
No matter how good your product roadmap and backlog are, they are only as good as your audience’s ability to understand your vision and priority.
The scrum master is like the conductor of an orchestra, ensuring that every piece fits together at the right time to create something greater than the sum of the parts. You don’t have to know how to play each instrument, but you do have to understand what each part contributes to the overall masterpiece.
Tools are important to product teams, but only when they support solid people and processes.
Aha! introduces scenario planning to give product owners the ability to create and compare multiple release approaches based on team capacity and backlog priority.
Adoption is one of the biggest challenges that organizations deal with when implementing commercial project management tools. Amid a global pandemic, this challenge has only been exasperated with many working from home.