“The most efficient and effective method of conveying information to and within a project team is face-to-face conversation.”
Continue reading
टैग: es-done
12 एजाइल सिद्धांत — 12 में से #5
“Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.”
Continue reading
12 एजाइल सिद्धांत — 12 में से #4
This principle emphasizes a partnership approach between the project team and the business sponsors. This is very consistent with the Agile Manifesto value of “collaboration over contracts.”
Continue reading
12 एजाइल सिद्धांत — 12 में से #3
“Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.”
Continue reading
12 एजाइल सिद्धांत — 12 में से #2
“Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.”
Continue reading
12 एजाइल सिद्धांत — 12 में से #1
“Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”
Continue reading
वॉटरफॉल मॉडल की समस्याएं क्या हैं?
In reality, customers may not know what their needs are until they see the software at work, so changing their requirements leads to redesign, redevelopment and retesting, and increased costs. Developers may design a new software product or feature without realizing the difficulties ahead, in which case it is better to modify the design rather than insist on a design that does not take into account any newly discovered constraints, requirements, or problems. As a result, there is no guarantee that the requirements the organization has in mind will actually work.
Continue reading
स्क्रम: साइनेफिन फ्रेमवर्क क्या है?
Cynefin Framework helps managers to identify how they perceive situations and make sense of their own and other people’s behavior. It draws on research into systems theory, complexity theory, network theory and learning theories.
Continue reading
स्क्रम प्रोडक्ट ओनर: भूमिका और जिम्मेदारियाँ
A Product Owner is responsible for telling what should be developed and the order of items that needs to be fulfilled. You can consider him as the sole authority that would tell the rest of the team what they need to create and which features should come first. In short, he is the one who tells the other members of the team about what they should be coming up with.
Continue reading
स्क्रम कैसे करें: एक व्यावहारिक मार्गदर्शिका
Scrum is a framework for developing and maintaining complex products and is an incremental, iterative development process. In this framework, the entire development process consists of several short iteration cycles, a short iteration cycle called a Sprint, and each Sprint is 2 to 4 weeks long.
Continue reading