Frequently Asked Questions About Scrum and Agile Training
Ekipa offers Scrum training around the world, in both public and private settings, to advance participants’ understanding and practice of Scrum. They include:
Private Courses and Coaching Services
Ekipa trainers are available for on-site courses and mentoring that can be tailored to an organization’s unique needs in their agile transformation.
Scrum Crash Course(Public and Private)
This is a two-day course on the principles and practices of Scrum. This course is a requirement for
Scrum Alliance Certified ScrumMaster (CSM) certification.
Web Based Training
This is a series of interactive self-paced training modules which covers the basics of Scrum and clarifies the purpose of Scrum’s different meetings.
For more information contact email@example.com
All of Ekipa’s public and private Agile certification courses are conducted by Scrum Alliance Certified Scrum Trainers. Ekipa’s Trainers are well known thought leaders in the Scrum community who speak regularly at industry conferences and contribute content to leading agile journals and publications. For more information on Ekipa Trainers, visit their blogs to read more about their thoughts on Scrum: http://blog.ekipa.co.id or read their profiles at http://www.ekipa.co.id/coaching.
No. Course attendees come from a variety of experience levels with Scrum. We find that people take the course for a variety of reasons, for example:
Their organization is moving to Scrum. / Agile
They want to kickstart success in their Scrum projects.
They want to become certified so that they can change roles or advance in their careers.
They want to refresh their skills.
They want to work with experts to help move through impediments they are facing in their Scrum transformations.
mis in faucibus.
This is a two-day course intended for anyone involved in the Scrum development process: i.e. developers, project managers, architects, technology consultants, business analysts, ScrumMasters, and Product Owners. Other functional stakeholders that work with Scrum technical teams also find the course valuable (executives, sales/marketing, finance, HR).
Agile practices focus on giving teams and individuals ownership of their work and accountability to the team and organization, so that you can care to make things better.
- To reduce a story in size ask what is the value of the story is and how can we deliver 80% of that value (in a shippable way of course).
- Don’t release on Friday.
- Create a table which shows who is present and who isn’t for the coming week
- The daily standup shall not exceed 15 minutes, unless you decide its ok of course 🙂 (Don’t decide too often, and only for learning purposes so that future Dailies are less than 15 minutes)
- To keep a daily short, don’t discuss in depth, save that for after the daily.
- An alternative for daily standup (what did/will I do) is what did I learn, what do I need to learn today and how you can help me
- A second alternative is 1) What do others need to know about the things I did yesterday, 2) What can I get from, or how can I collaborate with others to get things done effectively today, 3) What is blocking my effective work?
- The Scrum Master should have time to observe (eg not busy with 100s of tasks)
- A good PO is very important. Take some time in the beginning of the project to identify the constraints the PO has in terms of availability to the team, authority to make scope and budget decisions, domain knowledge, access to stakeholders.