Learning one new thing everyday
Scrum artifacts provide critical information that the Scrum team and stakeholders need to know in order to understand the product being developed, the activities being planned, and the activities being completed in the project. The following artifacts are defined in the Scrum Process Framework.
Continue reading
The completion definition (DoD) is a list of requirements that the user story must comply with so that the team can invoke it as complete. The acceptance criteria for user stories include a set of test scenarios that will meet the requirements to confirm whether the software works as expected.
Continue reading
Industry analysis is a tool to help companies understand where they stand compared to other companies that produce similar products or services; Understanding the impact factors across the industry is an important part of effective strategic planning that enables small business owners to identify threats and opportunities facing their business and focus resources on developing unique capabilities that provide a competitive advantage.
Continue reading
MVC (known as Model-View-Controller) is a pattern in software design that is commonly used to implement user interfaces, data, and control logic. It emphasizes the separation between the business logic and presentation of the software. This “separation of concerns” provides better division of labor and better maintenance.
Continue reading
UML activity diagram is another common tool used by UML to model the dynamic behavior of the system. It describes the sequence of activities and shows the flow of control from one activity to another. UML activity diagram is essentially a flow chart.
Continue reading
Test Driven Development (TDD) is a software development process, which relies on transforming software requirements into test cases before software is fully developed, and tracking all software development by repeatedly testing software for all test cases. This is the opposite of developing software first and then creating test cases. Some popular models support TDD very well, such as MVC and MVP.
Continue reading
A use case approach is a kind of technique for identifying the business goals of a system. The identification of use cases helps define system scope, ensuring that the requirements to be found will all be aligned with the business values, needs and strategy.
Continue reading
A use case is a requirements capture and documentation technique that can be written in plain text to describe in a narrative manner the actions and interactions of participants using the system. Finally, the functionality of the system should satisfy the purpose for which stakeholders use the system.
Continue reading
A Five Forces analysis can help companies assess industry attractiveness, how trends will affect industry competition, which industries a company should compete in — and how companies can position themselves for success.
Continue reading
Use cases are often graphical, and use case diagrams are supported by text descriptions, including use case and participant descriptions, as well as scenarios associated with use case templates that make use case methods simple and intuitive and ideal tools for discussing and clarifying developers’ understanding of user needs.
Continue reading