When does class start/end?
Classes begin promptly at 9:00 am, and typically end at 5:00 pm.
As a ICAgile Certified Professional designation course, this Agile training course offers hands-on practices in Iteration Planning, Product Roadmap and Backlog, Estimating Practices, User Story...Read More
As a ICAgile Certified Professional designation course, this Agile training course offers hands-on practices in Iteration Planning, Product Roadmap and Backlog, Estimating Practices, User Story Development and Iteration Execution. There is more to Agile development than simply a different style of programming. That's often the easy part. Agile development methods change your approach for requirements gathering, estimation, planning, team development, stakeholder interactions and more. While not a silver bullet, Agile Methodologies have become the most practical way to create outstanding software. We'll explore the leading Agile methodologies. You'll learn the basic premises and techniques behind Agility — so that you can apply them to your projects. The classroom will be broken up into Agile teams and your expert instructor will drive each team through the Agile process from planning through execution. Your instructor will answer questions with real-world experience, and you will leave the class with practical knowledge and a clear roadmap for your team's success.
Attendees who complete this course automatically receive the ICP designation after course completion, based on their exposure to the Agile Fundamentals learning objectives, which is covered in this course. The ICP designation verifies that the attendee has been introduced to these five areas through training:
Because this is an immersion course and the intent is to engage in the practices every Agile team will employ, this course is recommended for all team members responsible for delivering outstanding software. That includes, but is not limited to, the following roles:
Since the ICP is required to attain any ICAgile Expert certification, it is an excellent way to jumpstart your Agile career. You can include the industry–recognized designation in your signature, resumes, and also display your newly learned Agile skills from the class.
Teams will engage in a fun exercise that will reinforce the importance of, and power behind, self-organizing teams. As with sports teams, individual roles are important, but even more important is the need to work toward a common goal together. At times that means blurring the lines of traditional roles. Great teams will not define themselves by their individual roles.
Each team will conduct a brainstorming session for creating a product backlog in the form of user stories. Each team will present some of their user stories and the instructor will lead discussion about where teams hit the mark and areas for improvement (Instructor will not have all of the ideas, this is a great opportunity for team dynamic). After some feedback and sharing, each team will take a second pass at creating some user stories.
Teams are tasked with assigning a priority to their user stories at the appropriate level of detail.
Teams are tasked with assigning story point estimates to enough user stories to extend at least a few iterations into the future. The methods for determining the story point estimates will be Planning Poker and Affinity estimating. Teams will be given enough time to begin to see some consistency in their team and triangulate relative sizing of their stories. Teams are then asked to estimate their team's velocity.
Teams are tasked with discussing the details of the stories that, based on the estimated team velocity, may be completed in the first iteration. As the details are discussed, the tasks will be identified that would be needed to achieve the desired result. Next, with all of the tasks identified, teams assign actual time estimates to the tasks identified. Finally, the team will revisit the sizing of the iteration to determine if they have the appropriate time and resources to meet their commitment.
Taskboards are an invaluable communication tool during each iteration. Each team is tasked with coming up with their taskboard that communicates clearly their commitments for the iteration and progress against those commitments.
Teams will discuss what things they can do the day after class ends to take what they've learned and implement it immediately so that they don't lose what they've learned.