Onsite Course Designed to Accelerate Your Agile Led Alfresco Implementation
| Course Title: | | Agile for Alfresco Implementation Introduction |
Schedule: | | Two Day Onsite Agile Led Alfresco Implementation Coaching |
Target Audience: | | Product Owners, Business Analysts, Software Developers and Test Engineers |
Attendance: | | Maximum of 6-person session |
Location: | | Onsite/Client offices |
Bookings & Info: | | Email: info@monetical.com |
Introduction
The course starts with an introduction to the virtues of Agile methodology, including the Agile Manifesto, principles of an Agile change programme’s success, identifying who the key players are and highlighting a number of Alfesco implementation best practices. The core of the course will focus on explaining project implementation life cycle objectives using a number of hands-on workshop sessions. This will include successfully capturing and then transforming business needs into narrative Stories, developing a Project Roadmap, Sprint Planning (including estimating and task assignment), Daily Scrums (including stand ups and your Agile wall), Sprint Retrospectives and providing Stakeholder feedback.
1. Business Needs and their Stakeholders - Why Agile?
Session one pulls together a wealth of knowledge from Alfresco and Agile communities and the wider IT industry on how to successfully adopt Agile on an implementation project like Alfresco. During the first session the attendees will be provided with an introduction to Agile led Alfresco best practices, which can easily be exploited during each of these critical project activities. Examples will be provided that cover the following Agile led Alfresco project characteristics:
- Facilities hosting the project and users
- Information management capabilities
- Communication across the project communities
- Team appointed to deliver the solution
- Project methodology, techniques & reporting
2. Epics and Stories - The importance of developing a narrative
Project owners will develop an understanding of how to create a structured requirements management mechanism that ensures individual business needs and wants are clearly documented. This second session will also focus on the relationship rules existing between individual business needs and wants in order to aid the capturing and tracing of items with Stakeholders. The session finishes with an insight into how to create and manage a Product Backlog of project Epics and Stories that demonstrate how best to approach your Alfresco implementation.
Product Backlog
Time will be taken to explain how to focus on a single Stakeholder and their unique requirements. We will explain how Product Owners and Business Analysts can quickly get on with the task of developing the Product Backlog and the opportunity for the organisation to develop its own library of standardised Work Packs. These include the following activities that can be leveraged over any number of Sprints:
- Coding instructions
- Research and documentation
- Staffing and administration
- Testing options
- Sourcing options
Also included are explanations on how to efficiently capture a wealth of supporting materials as well as references to support material and suggested 3rd party products to use during your implementation.
Defining Stories
Thorough coaching will be given on how to efficiently convert user stories into implementation tasks. This critical activity forms the majority of the work undertaken by the Product Owner and Business Analysts prior to Sprint Planning. The rapid and accurate definition of achievable Epics and Stories is made possible because of the tasks that make up the standardised Work Pack. Special attention is given to customising these recommended tasks to meet the unique requirements of the project.
3. Sprint Planning - Converting stories into small focused tasks
The third session will focus on ensuring the team understands the appropriate tasks necessary to install and configure Alfresco. Explaining how to size Epics and Stories for both Server and Client side requirements help the team develop confidence in its Sprint Roadmap using story points and developing an ever-increasing accuracy of the Sprint Velocity. We also show how the output from Sprint Planning sessions are comprehensive due to the fact that all the individual tasks are well documented, assigned to individuals, prioritised and all the currently available supporting material is provided.
4. Scrums - Daily performance checks
Through role-play, a factious daily scrum shall be used to demonstrate how this daily activity is a great way to monitor project progress, encourage project collaboration and ensure project challenges are quickly brought to the attention of the entire team. Working in sync with a mocked-up Sprint Agile Wall guidance on how and when to operate the individual tasks cards, swim lanes and recording ‘blockers’ and actual tack ownership will make for one of the most enjoyable sessions. Time will be spent explaining the main Scrum Master role and their responsibilities, including, dealing with project blockers, scope change and generating a burn down chart. Furthermore, focus will be given on how to maintain the relationship between individual Sprint tasks and the high-level Sprint. Sprint members have immediate access to a wealth of support material, including associated wikis and forums.
5. Retrospectives - What went right and what needs improving
How to develop an active knowledge ecosystem within the project shall be the focus of the last but one session. Demonstrating, through role-play, how to formally solicit and record sprint experience against five primary characteristics (Process, Operations, Resources, Knowledge and Communication), and how to efficiently diagnose root causes and plan the appropriate corrective measures during the following Sprints. The session will also detail how the Scrum Masters should pull together all the appropriate sprint performance details (i.e. risk assessment, change records and sprint performance charts) for the current Sprint and how it should be integrated to measure overall project performance and risk.
6. Showing the Business the Sprint deliverable
The benefits of soliciting feedback from the Stakeholder and end user community through the hosting of ‘show and tell’ sessions that conclude each Sprint shall be discussed. How this timely feedback is rolled into the next Sprint planning session will be covered, which results in a 360 degree project cycle.
|