Going Vertical; A Value Driven Approach to Web Development
One of the biggest development hurdles we face when new to any agile framework is switching from a ‘phased’ approach to a ‘vertical slice’ approach. Individuals and teams often aren’t used to deconstructing projects and problems in this way and we often hear “what about the dependancies” or “the system is too complex”.
In order to speed up feedback loops and provide instant value to clients, we can take a large feature and break it up into several small pieces that slice through each of the systems architectural layers. We can break down almost any of the features we do within projects into slices that take a couple of days, at most, to get out the door. Each slice is comprised of any work needed to be done in a system architectural layer, as well as, any testing that may need to be done to make it ready for deployment.
Outline/structure of the Session
In this session, Steve will demonstrate, through slides and discussions, the advantages of vertical slicing and will walk you through some real-life project examples of how to implement this agile approach to Web Development.
In this session, Steve will teach you how to actually apply this approach into your organization or agency. He will also show the advantages from the perspectives of the Project Manager, Product Owner, Scrum Master, Development Team, and the Client.
This session is for you if you:
- Work on any web-based projects, of any size.
- Have ever struggled to provide value to your clients throughout the entire project; from start to finish.
- Are new to agile development and want to learn more about different approaches as it ties directly to web development.
Web Developers, Project Managers, Development Managers, Team Leads, Technical Leads
There are no session prerequisites.
schedule Submitted 1 month ago
People who liked this proposal, also liked:
Lisa Fast - Not too minimal: UX research in a Government MVPLisa FastUX UnicornVation Inc.
schedule 1 day agoSold Out!
Lean UX research is essential to guide and validate what exactly is the 'Minimum Viable' to launch a Minimum Viable Product, especially in government.
In this talk, I'll describe how user research insights helped us understand, design and launch Canada's first online open-source regulatory consultation. The first research participant identified a significant hole in our assumptions - and predicted that we could miss the minimum viable mark. It helped us course-correct, and plan ahead for the next development iteration.
The other customer group was the government. We applied lean UX research techniques to understand the government analyst team's journey and needs, and then to co-design with them as the analysis site MVP was developed, and as the commenter data flowed in.
I'll describe how the insights from the research helped us meet the Minimum Viable mark for the government customers, understand how and why we missed the mark with the specialist customers and how you can apply lean UX research techniques to ensure you don't iterate your way to a useless product.
Ken McMillan, PMP, CISSP, ITIL, MIPIS, PCIP - That's nice and you're nice ‒ but I don't care: Aligning service-delivery to business requirements in the public sectorKen McMillan, PMP, CISSP, ITIL, MIPIS, PCIPSenior AdvisorOffice of Small and Medium Enterprises, Public Services and Procurement Canada
schedule 2 weeks agoSold Out!
In the federal public service there is an almost-complete disconnection between the performance evaluation criteria applied to business leaders and the criteria applied to service providers.
As a consequence, even in situations where both the business and the service provider enjoy optimal relationships, the goals are not the same and may even be entirely contradictory.
In a climate centered on Results and Delivery, leaders cannot expect results if they do not mitigate this conflict.
The approaches proposed in this discussion align the service organization to the business. They promote mutual accountability by insisting on mutual performance alignment between the business and its services provider.
Ron Ijack - Why we got rid of SCRUM to become agile againRon IjackVP TechnologyUpstream Works Software
schedule 2 weeks agoSold Out!
Agile is not about doing scrum, kanban, lean or any other flavour of the process. An organization cannot be “doing” agile, they must “be” agile. They must believe in and understand the agile principles. After going through a successful agile transformation and running scrum for 3 years we realized that it’s just not working for us anymore. The team was suffering from scrum fatigue. It felt like there was a sprint planning, stand up or retrospective meeting happening all the time. We decided to take a hard look at how we were working and turn it on its head. We looked at all the different agile options such as scrum, kanban, lean, xp, etc and decided to take the best part from all of these instead of sticking with one approach. This session will take you through our journey and share what worked for us that could also work in your organization
Steve Lavigne - Doing Agile != Being AgileSteve LavigneProduct OwnerOPIN Software Inc.
schedule 1 month agoSold Out!
There is a very real misconception that people believe....just because they have a daily stand up once in a while or because they only plan work for the next week at a time that they are being agile. This simply could not be farther from the truth.
Doing agile does not mean you are being agile!
Just because you have a stand-up, does not mean you are being agile. Just because you only plan work for the next week, does not mean you are being agile.
There is a lot more needed for a company or a team to be agile and it is a lot harder than you think....but understanding the difference is half the battle.