“A Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team” — Scrum Guide. In contrast to the component team approach, a cross-functional teams are groups consisting of people from different functional areas of the company. — it should be formed not only with technical specialists (Back-end, Front-end developers, QA engineers, etc.) but also consists of members like Business Analysts, Marketing and UX specialists or anyone else taking an active part in the project.
Continue readingPenulis: vpadmin
What is Reverse Brainstorming?
The reverse brainstorming lets you create unusual and wild ideas if the brainstorming process fails to meet the requirements. When typical brainstorming encounters difficulties, it’s time to be creative. A highly creative brainstorming technique is called reverse brainstorming. It can not only make ideas flow, but also bring a lot of fun. More importantly, it can stimulate innovative ideas and useful insights to produce positive results.
Continue readingBrainstorming Techniques Toolkit
Brainstorming is a group creativity technique by which efforts are made to find a conclusion for a specific problem by gathering a list of ideas spontaneously new ideas and possibilities. It’s a classic method widely used in business activities such as problem-solving, failure analysis, new product ideas, sales increasing, product improvements, etc.
Continue readingWhat is Case Management Model and Notation (CMMN)
CMMN is a graphical notation used for capturing work methods that are based on the handling of cases requiring various activities that may be performed in an unpredictable order in response to evolving situations. Using an event-centered approach and the concept of a case file, CMMN expands the boundaries of what can be modeled with BPMN, including less structured work efforts and those driven by knowledge workers. Using a combination of BPMN and CMMN allows users to cover a much broader spectrum of work methods.
Continue readingHow to Perform Gap Analysis with BPMN?
Gap analysis involves the comparison of actual performance with potential performance. For example, a company does not make the best use of current resources, it may perform below an idealized potential. In other words, gap analysis is the process people use to examine their current state (or as-is process) with their desired state (to-be process) of a company. It typically is used to determine if the company is meeting expectations and effectively using resources that measure time, money and labor. The management team can then create an action plan to move the organization forward and close the performance gap.
Continue readingScrum Guide Change: Self-Organizing vs Self Management Team
Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team.
Continue readingCross-Functional Flowchart – with Templates and examples
Cross functional flow charts show who did what and when in swimlane or grid charts. These charts are organized into multiple parts to provide additional dimensions by assigning each process step to a category. In other words, you can use a cross functional flowchart to describe the relationship between the steps in the process and the department or functional area responsible for those steps.
Continue readingUse Case Diagram vs Use Case Specification
A Use Case describes a task that is performed by an actor yielding a result of business value for a business. A use case may be visualized as a use case diagram or/and in structured textual specification format:
Continue readingThe Agile Manifesto and Twelve Principles
Agile is a philosophy of providing solutions that encompass and facilitate evolutionary change throughout the life cycle of a product/project. Many agile teams and organizations have been using Agile to deliver software faster, improve quality, and ultimately improve customer satisfaction.
Continue readingWriting Good User Stories
User stories are part of the agile approach and help shift the focus from writing requirements to discussing them. All agile user stories include one or two written sentences and, more importantly, a series of conversations about the desired functionality.
Continue reading