Hi George, yes it is part of the same presentation. The two parts are part of the same Webinar.

Chapters 1 and 2.

No Luis, we will prepare you for the SFC^™ certification exam in this webinar/training. Although, it will be a good idea to go through the online course just to revise the concepts.

Hi Kyle, you can take the exam as per your convenience, but I would recommend the quicker you attempt the exam, the better so that the concepts studied today still remain fresh in your mind when you attempt the exam.

Hi Matt, there are two options. Either you can go through the recording of this webinar which we will be emailing to your registered email address or you can join the next webinar an hour late.

If the team is not able to deliver a task in a Sprint, the retrospect Sprint should discuss what went wrong. Was it to do with lack of clarity of the requirement or if there was some issue with calculating the velocity or if the estimations were off? Also, the unfinished task will then have to be reprioritized against the remaining user stories and included as part of the coming Sprint.

Done Criteria is a checklist of the types of work that the team is expected to successfully complete by the end of the sprint, before it can declare its work to be potentially shippable. A team’s definition of done should be determined before it does its first sprint. SBOK^® recommends against weakening of Done Criteria in a sprint. If the PO thinks it imperative, Done Criteria can change for the next Sprint based on the requirements.

There is no set format but it must be objective/measurable. So, the page should load fast is not an Acceptance Criteria. The page should load in 1 millisecond can be an Acceptance Criteria.

Scrum can be used for any type of project. You can use Scrum framework to deliver project's products and comply with the standards and regulations through a role called Scrum Guidance Body. This role will be discussed later in the webinar. Also, you can always tailor the Scrum framework depending on the type of project you are working in. Scrum recommends creating only those documents that you really need for the project and not create a document just for the sake of creating it.

Manufacturing is not a project. However, if you are creating a prototype, then even an individual part of the car can be considered as a deliverable which the customer (technical/manufacturing teams) wants to see. Think of building an ecommerce website - instead of building all features before releasing (which could take you years), you could build the website features with maximise ROI and open up for customers. Then progressively keep adding new features based on changing customer requirements.