In my previous article, I mentioned about User Story, Theme and Epic concepts and focused on their functional assistance, you can find the article on the following link,
Time to ask the right questions
Like any other cultural change, DevOps requires a real mindset shift. It won’t happen overnight and like all good things it doesn’t come free, we have to pay for it.
To increase agility and quality of software lifecycle, DevOps is a term that calls for closer collaboration between the teams that touch the software lifecycle, namely development and operation teams.
There is a strong connection between agile methodologies and DevOps concept.
After Scrum methodology settled into the organizational culture, there are some issues that cause confusion and communication problems. First of all, we should not forget that the aim of all these descriptions are only for creating a common language in the organization. That is why, if you already have the common terminology for these definitions, it is alright to keep going with them. In this article I address the well accepted description of these concepts.
In my previous post, I focused on the philosophy of the PSPO I (Professional Scrum Product Owner) exam and mentioned about to whom this exam is related to (http://all4agile.com/en/professional-scrum-product-owner-pspo-exam-story-episode-i/). In this continuation post, I will touch the methods of studying, sources that needed to be studied and reply the question how you should study to guaranty to get the certificate. You can achieve the information about concept of the exam, application steps and tips about the exam in this article. I prepared my advices point by point to create the functionality of a to do list. When you mark as done to all bullets and read over first episode of the post, you can take the exam confidently.
Scrum processes address the specific activities and flow of a Scrum project. The main processes can be summarized as Initiate, Plan and Estimate, Implement, Review and Retrospect, Release.
The last three phases; “Implement, Review and Retrospect, Release” will be introduced in this article.
Sprint planning is a set of activities enabling product requirements submitted by a Product Owner to be met within 2-3 weeks periods. During planning process Product Owner, Scrum Master and Scrum Team attends to Sprint Planning Meeting. In general, these meetings are hold in two sessions, one of which is a kick-off meeting, Product Owner’s explaining the requirements to team, and the other is team breaking out and estimating tasks.
I mentioned about the Product Owner role in the organizations, incorrect decisions about this positioning and responsibilities of the Product Owner in the period of agile transformation in last month’s blog post. You can find it from the following link (http://all4agile.com/en/positioning-product-owner-role-in-organizations/). This month, I will focus on the exam, that proofs the ability of the candidates about Scrum Product Owner, and answer the questions of; the index of the exam, fits for whom, application lifecycle, tips and the tricks about the exam.
An ERP project consist of following components. In this and upcoming blogs we will try to answer what we can do in terms of being agile within each component. This blog covers the “Using the Program and Defining Requirements” and “Design” components.
Information technology methods and systems ease gathering data and performance measurement. Although it is not always possible to model real life, without assessing the quality of input and output data, quantitative values can be obtained so as to measure performance. Unlike traditional project management, specific performance measurement approach was redesigned for Scrum models and its metrics were taken place in literature. These metrics can be explained as the following.