tag:blogger.com,1999:blog-6516117921148424202024-02-21T08:03:57.087-08:00QuickScrum Scrum Community - It's all about Scrum!The QuickScrum community offers a single, common platform for all Scrum people to meet, talk about, and understand Scrum. The community offers endless possibilities for Scrum professionals, coaches, and trainers to find business opportunities. Scrum professionals can participate in events, coaches can hold workshops and share knowledge through articles and videos, companies can post Scrum job requirements, while Scrum beginners can learn Scrum from the vast knowledge base. Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.comBlogger81125tag:blogger.com,1999:blog-651611792114842420.post-65595502961712778742016-04-11T03:02:00.003-07:002016-04-19T03:10:26.774-07:00Distributed Teams Challenges And Agile Advantages<div dir="ltr" style="text-align: left;" trbidi="on">
<div style="text-align: center;">
<h1>
<span style="font-family: "trebuchet ms" , sans-serif; font-size: large;"><b>Distributed Teams Challenges And Agile Advantages</b></span></h1>
<br />
<span style="font-family: "trebuchet ms" , sans-serif; font-size: large;"><b>Part 1 - Project management methods and Agile</b></span></div>
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span>
<br />
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">With dynamically changing market scenarios dominating the outsourcing markets, it has become imperative to remain conversant with emergent technologies and use them for developing projects. New platforms and technologies have a lot to offer in terms of reduced development time and targeting a wider range of client-centric requirements, however, while reaping the benefits they offer, they also impose a few constraints regarding their applicability. <a href="https://www.quickscrum.com/Home/ScrumSoftware" target="_blank"><b>Offshoring businesses can increase the productivity</b></a> levels and generate higher profits but often face problems in finding technical teams familiar with the usage and implementation of new technologies. For most organisations, it is more profitable to find technical talent in other countries and outsource their projects depending upon the nature and scope of the project on hand. </span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">It is very important to manage projects in an effective manner to make them profitable. Several project management frameworks and methods aim to make project management easier and more effective. Some of the popular methods used in the past, and even now are:</span></div>
<br />
<ul style="text-align: left;">
<li><span style="font-family: "trebuchet ms" , sans-serif;">Critical Path Method (CPM)</span></li>
<li><span style="font-family: "trebuchet ms" , sans-serif;">Critical Chain Project Management (CCPM)</span></li>
<li><span style="font-family: "trebuchet ms" , sans-serif;">PMI/PMBOK Method</span></li>
<li><span style="font-family: "trebuchet ms" , sans-serif;">Event Chain Methodology (ECM)</span></li>
<li><span style="font-family: "trebuchet ms" , sans-serif;">Extreme Project Management (XPM)</span></li>
<li><span style="font-family: "trebuchet ms" , sans-serif;">Adaptive Project Framework (APF)</span></li>
<li><span style="font-family: "trebuchet ms" , sans-serif;">Lean Development (LD)</span></li>
<li><span style="font-family: "trebuchet ms" , sans-serif;">Six Sigma/Lean Six Sigma</span></li>
<li><span style="font-family: "trebuchet ms" , sans-serif;">PRINCE2</span></li>
<li><span style="font-family: "trebuchet ms" , sans-serif;">Dynamic Systems Development Model (DSDM)</span></li>
<li><span style="font-family: "trebuchet ms" , sans-serif;">Feature Driven Development (FDD)</span></li>
<li><span style="font-family: "trebuchet ms" , sans-serif;">Rapid Application Development (RAD)</span></li>
<li><span style="font-family: "trebuchet ms" , sans-serif;">Systems Development Life Cycle (SDLC)</span></li>
<li><span style="font-family: "trebuchet ms" , sans-serif;">Waterfall (Traditional)</span></li>
</ul>
<br />
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span>
<br />
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">Each method proposes to make <a href="https://www.quickscrum.com/" target="_blank"><b>project management easy and more accurate</b></a>. Often, it is difficult to choose which method one ought to adopt for developing a project since every management technique has its own pros and cons. While a particular organisation may offer a positive feedback regarding a method it is following, consultants might consider it a bad choice and speak against it. There are no postulates or rules which define a “successful” project. Also, there are no rules which can help in deciding whether a particular methodology is more effective as compared to the other. It is based more upon personal experience, understanding how a methodology works and what it has to offer, and how well it can be implemented. Perhaps, the most important aspect to understand is whatever methodology you choose, what is more important is how well you use it to your benefit to make your project successful.</span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">Projects may vary in terms of their scope, size, complexity, and nature. However, regardless of that, offshore or distributed teams have to be properly coordinated and managed. Agile project management framework offers several options for managing remotely developed projects.</span></div>
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span>
<span style="font-family: "trebuchet ms" , sans-serif; font-size: large;"><b>Agile frameworks</b></span><br />
<span style="font-family: "trebuchet ms" , sans-serif;"><b><i>Scrum</i></b></span><br />
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">Recommended for developing small to medium sized projects using a team of 7 to 12 cross-functional and multi-skilled individuals. The Scrum framework is characterized by its clearly defined events, artefacts, roles, and process which have to be followed by the entire team. The error correction and retrospection activities take precedence over documentation and delegation of authority. The client is actively involved in verifying the development carried out by the team. The Scrum team delivers the business value in the project through successful product increments developed through periodic cycles known as sprints.</span></div>
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span>
<span style="font-family: "trebuchet ms" , sans-serif;"><b><i>Extreme Programming (XP)</i></b></span><br />
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">Extreme Programming (XP) offers a practical approach to program development and focuses primarily upon the delivery of business results. It follows an incremental, start-with-something approach towards product development, and makes use of continued testing and revision processes. XP is generally recommended for short-term projects, and development teams typically follow code-test-analyse-design-integrate process. XP is known for “paired” programming i.e. two developers engaged with code development and testing simultaneously. One programmer creates the code while other tests it on the spot.</span></div>
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span>
<span style="font-family: "trebuchet ms" , sans-serif;"><b><i>Kanban</i></b></span><br />
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">Based upon the concept of Toyota production model, Kanban offers a pragmatic approach to development by matching the actual amount of work in progress to the development teams capacity in delivering it. The framework provides more flexibility in terms of planning options, quicker output, a clear focus pertaining what needs to be developed, and maintaining total transparency throughout the product development cycle. </span></div>
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span>
<span style="font-family: "trebuchet ms" , sans-serif;"><b><i>Scaled Agile Frameworks (SAFe)</i></b></span><br />
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">Scaled Agile Framework (SAFe) is a structured and prescriptive method to help large organisations and enterprises to get started with adopting Agile. It is a popular and efficient Agile framework successfully used by many companies covering various industry verticals. It is specially recommended for <a href="https://www.quickscrum.com/ScrumTool" target="_blank"><b>large sized software based projects</b></a> where teams can function interdependently.</span></div>
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span>
<span style="font-family: "trebuchet ms" , sans-serif;"><b><i>Nexus</i></b></span><br />
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">Nexus is an Agile framework focusing upon cross-team dependencies and team integration issues. It facilitates Agile implementation in complex and large scale projects. It functions as an exoskeleton and helps multiple Scrum teams to integrate and pursue a common goal of delivering valuable product increments through sprints. Each team delivers a certain business value to the client through each product increment cycle, and the teams achieve this by following Agile principles and process. Nexus is recommended for development teams consisting of over 100 individuals.</span></div>
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span>
<br />
<div style="text-align: center;">
<span style="font-family: "trebuchet ms" , sans-serif; font-size: large;"><b>Part 2 – Agile for distributed teams</b></span></div>
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span>
<br />
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">While executing your very first remote project, the most logical thing to do is to document the project vision and figure out how the team will deliver the project goals. Proper and effective communication is of paramount importance while explaining the goals and objectives to team members. It is a simple and straightforward process most of the times, but while working with distributed teams, the cultural differences and varying language proficiency levels may often create constraints and lead to miscommunication as well as confusion. This can be a common scenario in case of teams located in countries across different time zones and possess limited ability to communicate using a particular language. Individuals may find it difficult to understand and capture the exact project requirements and deliver code or functionality that does not fulfil end user requirements. Projects often fail because of these and other such technical and non-technical reasons.</span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">Using Agile it may be possible to simplify these types of problems. Agile is not a silver bullet that can rectify all issues and problems faced during project execution. Agile is a framework, therefore It depends upon how well the team understands its principles and how effectively it implements them in the project. However, the framework is designed such that issues can be dealt with in a more proactive and effectual manner.</span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span></div>
<div style="text-align: center;">
<span style="font-family: "trebuchet ms" , sans-serif; font-size: large;"><b>Part 3 – Dealing with issues using Agile</b></span></div>
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span>
<br />
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">Businesses opt for remote or distributed teams mainly to segregate the development activity from the main organisation body by trans-locating the team and development activity to some other location for management or financial reasons. The team is directly employed by the organisation and each member is an employee. In case of offshoring, the entire project is outsourced to a development vendor who executes the project on behalf of the client, or develops it as a part of client contract. This discussion does not try to differentiate between whether the remote team is a part of parent organisation or it belongs to an outsourcing vendor. Some common issues faced while working with both types of teams are discussed and how those issues can be properly targeted using Agile. It is worthwhile to know that Agile is not the only project management platform to develop IT or software projects. Neither does it offer a guaranteed way of dealing with issues faced while working with or employing remote teams. However, the framework is uniquely designed, and is flexible enough, to deal with such issues in a more effective manner, and more easily.</span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span></div>
<span style="font-family: "trebuchet ms" , sans-serif;"><b>Project vision and documentation</b></span><br />
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">The project vision explains the goals and project deliverables. The primary aim of the <a href="https://www.quickscrum.com/Home/AgileTransformation" target="_blank"><b>team should be to deliver work supporting the vision</b></a> so meaningful business value can be delivered to the client. Often, development teams put in efforts and deliver work, but when reviewed by the client, it is discovered that the features developed don’t exactly support what the client actually wants. This can be a very common scenario when teams are unclear about what the project aims to achieve and why it exists in the first place. Common reason why teams may fail to understand the vision could be language barriers (In case of distributed teams located in different countries and speaking different languages) or a lack of proper communication from the client’s or management’s side explaining the objectives.</span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">Agile does not emphasize upon extensive documentation. In real life scenarios elaborate or extensive documentation often remains locked away in filing cabinets or resides on shelves for future references - teams rarely bother to read them thoroughly since they can be large in size and a lot of time is spent in reading and understanding them. The attitude of most development teams (Don’t mean to disrespect them in any way) is to get started with work so deadlines can be met. Teams are generally pressed for time so they don’t bother, or can’t afford to spend hours reading comprehensive documentation. Paperwork is greatly reduced in Agile, and if you choose to follow Agile, you need to create just enough documentation to get started with work. More importance is given to understanding client-centric requirements and delivering business value, rather than creating elaborate reports and documents. Moreover, one of the responsibilities of the product owner in Agile is to ensure that the team understands the deliverables and project vision properly before it starts to work. The PO also makes sure that the business value delivered from the sprints is useful and matches the project vision.</span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span></div>
<span style="font-family: "trebuchet ms" , sans-serif;"><b>Maintaining quality standards</b></span><br />
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">Quality and deadlines are two most important factors associated with, and affecting, the success levels of a project. Quality features fulfilling end user requirements have to be developed within the decided time so it can be properly marketed and business returns availed from it. In the IT market segment it is not just important to build quality software, but to release it in the correct manner at the correct time and at the correct place (targeted market audience i.e. the geographical boundaries within which end users are likely to buy your product. With online marketing these boundaries remain virtual but nevertheless play an important part in deciding the “target audience” when the project is planned and incepted). When outsourcing work to remote teams, the quality aspects could get compromised upon if a QA or testing process in set up as a part of development process. Fewer development teams actually bother to test the code for regression after it is developed unless it is a pre-decided activity and integrated with the development process.</span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">The Agile manifesto states "Our highest priority is to satisfy the customer through early and <a href="https://www.quickscrum.com/Home/AgileTraning" target="_blank"><b>continuous delivery of valuable software</b></a>." It emphasis upon “early and continuous delivery of valuable software” i.e. useful and valuable product features should be developed and delivered to the client on regular basis. Agile focuses upon the delivery of “shippable” features. Each feature should be properly tested for errors and made bug free before its development can be considered as complete and deployable. Developers and programmers often double as testers to carry out the QA part during sprint cycles. Agile fails if “workable” features are not developed. Remote teams trained in Agile have to fulfil the test conditions stated in the acceptance criteria defined for each development task created in the product backlog (ideally).</span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span></div>
<span style="font-family: "trebuchet ms" , sans-serif;"><b>The supervisor or project manager’s role</b></span><br />
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">Every project needs a manager to oversee its execution and completion. It is important for the supervisor or the project manager to remain available to the team and resolve problems and issues as and when they occur. When teams are located on-premises it becomes easy to resolve technical problems since face-to-face interactions are possible and the manager is always available when you need him or her. That is not always the case with remote or distributed teams. Owing to time differences, the manager could be ending the day while the remote team would be just about to start with work. Teams may be required to wait for some time before problems are resolved, and this could delay work further. Deadlines and commitments may therefore not be met. </span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">The <a href="https://www.quickscrum.com/Home/AgileDevelopment" target="_blank"><b>Scrum Master’s role is very clearly defined in Agile framework</b></a>. The SM often plays a servant-leader role, and mentors and facilitates the Agile process. The SM ensures that he or she is always available to the team and resolves glitches whenever the team gets stuck. In Agile, the Scrum Master is a specific role played by a person, rather than a designation or responsibilities given to a single individual. The role can be played by anyone in the team. In case of distributed teams, a responsible team member can be taught to play the Proxy Scrum Master’s role and provided with quick-access channels to communicate with the actual SM or PO in case of urgent issues. The person also functions as a team representative and creates daily feedback reports which can be studied by the client, PO, and the SM as per their convenience.</span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span></div>
<span style="font-family: "trebuchet ms" , sans-serif;"><b>Ownership and team empowerment</b></span><br />
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">Traditional project management methods differentiate between senior and junior level individuals, and have a clear hierarchical structure defining authority levels and who reports to whom. Even today, most organisations still follow this traditional hierarchical model, and individuals belonging to different levels of authority remain concerned about their responsibilities and reporting status. Even though the model is organised, it takes a lot of time for issues to get resolved as the escalation process involves several individuals starting from the junior level to senior levels. Moreover, people have a tendency to “pass on” issues to senior levels personnel and let them decide what to do next. Technical staff and junior level employees may prefer not to get involved with decision making since they often become scapegoats to bureaucratic procedures. In case of distributed teams the scenario can become even worse because you don’t have to deal with just bureaucratic attitudes but the language and distance factor may further make the team even less accountable for the success or failure of the project.</span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">Agile does not believe in shifting responsibilities or escalating issues. As per the model, teams are cross-functional and self-managing. Each team member often takes up additional tasks other than his or her particular skillset thereby reducing the total numbers of skilled members required in the team. There are no senior-subordinate levels – just three primary roles of product owner, scrum master, and the development team. Rather than assigning tasks, each team member voluntarily takes up work based upon his or experience and skills. One of the most important aspect about Agile is that the team has to “own” the project on behalf of the client. It means each person is responsible not just for the work done by him or her, but the overall contribution of all members at the team level is even more important. The entire team is accountable for the success or failure of the project – not just <a href="https://www.quickscrum.com/Kernel/CoachList" target="_blank"><b>the product owner</b></a> but each and every member of the team.</span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-family: "trebuchet ms" , sans-serif;">Moreover, the three roles of PO, SM, and the team are empowered in Agile to decide on their own what course of action to take to best fulfil their objectives. The development team is not required to follow orders or take permissions in deciding how a particular feature should be developed, and in what manner. It has to deliver work as decided in an event – the sprint planning meeting – held before each product incremental cycle known as a sprint starts.</span></div>
<div style="text-align: justify;">
<br /></div>
</div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0Clichy, France48.904526 2.304767999999967348.883651 2.2644274999999672 48.925400999999994 2.3451084999999674tag:blogger.com,1999:blog-651611792114842420.post-23673176820200322022016-03-18T03:37:00.001-07:002016-03-18T03:37:14.029-07:00Can Agile Reduce Complexity?<div dir="ltr" style="text-align: left;" trbidi="on">
<div style="text-align: justify;">
Every project has a certain level of complexity in it. When we say a project is simple, we actually mean that its degree of complexity is very less or can be considered as negligible, but nevertheless, it does exist even if in a minute magnitude. Project management methods deal with project complexities depending upon how flexible they are, and what kind of provisions they offer to deal with them. Tradition management methods such as Waterfall are often rigid owing to their “staged” working processes, which are also often irreversible. Using pre 1990 era methods, one can try to address the complexity in a project to a lesser or greater degree of success, but typically such management methods do not make it possible to reduce or minify the actual level of difficult in executing the project and neither its complexity. This is not necessarily true in case of Agile. With Agile you can actually try to control the level of complexity in a project provided you have the correct level of experience in <b><a href="https://goo.gl/f0rRyV" target="_blank">implementing Agile principles and techniques</a></b>.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEitUk0j3KSZw2WJ0qKHnjvID_u2hB9APg8qSeIvUl3V1vUd6VNdC-ocVfb24IM_17QBjvq8t0LJWducFELLv3gA5jO2vmhSSYFMOM5tRCB7SMoThe1IzaRnYkT2tKHPYBaxvY9oIARib_Uy/s1600/Can+Agile+Reduce+Complexity.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Agile Project Management" border="0" height="240" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEitUk0j3KSZw2WJ0qKHnjvID_u2hB9APg8qSeIvUl3V1vUd6VNdC-ocVfb24IM_17QBjvq8t0LJWducFELLv3gA5jO2vmhSSYFMOM5tRCB7SMoThe1IzaRnYkT2tKHPYBaxvY9oIARib_Uy/s400/Can+Agile+Reduce+Complexity.png" title="" width="400" /></a></div>
<br />
<h2>
What is "Complexity" in a project?</h2>
Broadly speaking the term "complexity" can be best understood as difficult or complicated conditions arising due to the availability of multiple options, or options which make you simultaneously focus upon different directions at a given time, and which result in a multi dimensional scenario that is hard to understand and resolve. Complexities can be of different types in a project. Business level complexities arise due to uncertain market conditions, technological advancements, and other such factors which affect the business logic contained in the project. The project level complexities can be of two types – project complexity and requirements complexity.<br />
<br />
<h2>
Project complexity</h2>
Project related complexity can be different of different types of organizations. Several factors contribute to it, however, the most important ones are uniqueness, limiting factors, and uncertainty.<br />
<br />
<ul>
<li><b>Uniqueness</b></li>
</ul>
<b><a href="https://goo.gl/HJ5aYj" target="_blank">Every project is unique and has its own attributes</a></b> and requirements. As the project commences it gains maturity over time and benefits through the learning process. This is most significant when the organization is running a project which is the first of its kind, or if it has no prior experience dealing with projects.<br />
<br />
<ul>
<li><b>Limiting factors</b></li>
</ul>
Projects are subjected to certain factors which can affect its execution or commencement such as budget constraints, the technical knowhow of the team, working schedule, and at times even cultural differences.<br />
<br />
<ul>
<li><b>Uncertainty</b></li>
</ul>
Uncertainty in a project can be due to external or internal factors. External factors may include government imposed rules and regulations, uncertain market changes, and fluctuating economic climate. Internal factors may comprise of the levels of management’s participation in the project, constantly changing company policies, stakeholders’ involvement in the project, etc. All these factors affect the scope of the project.<br />
<br />
It is a known fact that a project’s complexity affects its success. The manner in which a business anticipates, fully understands, and addresses the complexity determines whether a project is going to be successful or not.<br />
<br />
<h2>
Can Agile reduce complexity?</h2>
In traditional project management methods, the complexity in a project is often managed by investing a certain amount of time in the “analysis phase” with the sole objective of analyzing the levels of complexity and ... <span style="background-color: #93c47d;"><span style="color: red;"><i><a href="https://goo.gl/sLdbMF" target="_blank"><b>Read more</b></a></i></span></span></div>
</div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0Clichy, France48.904526 2.304767999999967348.883651 2.2644274999999672 48.925400999999994 2.3451084999999674tag:blogger.com,1999:blog-651611792114842420.post-34424538125791662032016-01-07T22:57:00.000-08:002016-07-13T04:07:57.771-07:00Types Of Agile Coaches And What Do They Do?<div dir="ltr" style="text-align: left;" trbidi="on">
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><img alt="Agile Coach" border="0" height="384" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEimE0sp5B6g7CdSnyB8OGzNYfPJ9voyXLYi2AaoKnVF3haiq4RdW7UJzjT8M8MkRsF1q-a-dtSQLqZyWXEQxRCd5nyWan0ApLfG6ffrPNVBTbBKqmtkMnX7gkQ_lk7rofezzFgyUCSI_Cee/s640/Types+Of+Agile+Coaches+And+What+Do+They+Do_Title+change.png" style="margin-left: auto; margin-right: auto;" title="" width="640" /></td></tr>
<tr><td class="tr-caption" style="text-align: center;"><br /></td></tr>
</tbody></table>
<div style="text-align: justify;">
<span style="font-family: "verdana" , sans-serif;">People may or may not have heard about the word “Scrum”, but for those who have, a question most commonly asked by them might be “What can Scrum do for me to improve my business?” or “How do I use Scrum to grow?” – A topic most discussed by CEOs, CTOs, project managers, and other senior level executives in a development company or organisation when they are faced with choices of adopting a framework to better their work processes and increase the investment returns for their organisation. It is important to understand that for a business new to Agile and Scrum a lot depends upon what type of Agile or Scrum coach it hires, and how successfully the coach can help the organisation to adopt Agile principles.</span></div>
<br />
<div style="text-align: justify;">
<span style="font-family: "verdana" , sans-serif;"><br /></span></div>
<span style="font-family: "verdana" , sans-serif;"></span><br />
<div style="text-align: justify;">
<span style="font-family: "verdana" , sans-serif;">Agile can work wonders for you provided it is implemented in an effective way. Agile coaches ensure that business implement the framework in a proper manner. Therefore, a lot depends upon what type of Agile coach do you actually need? You may feel unsure about Agile adoption but serious enough to “give it a try” and see if it can benefit you. On the other hand, you may be aware about the benefits of using Agile but not certain how to start. It’s worth considering about the level of Agile coaching you actually need to get started.</span></div>
<span style="font-family: "verdana" , sans-serif;">
</span><br />
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<span style="font-family: "verdana" , sans-serif; font-size: large;">What is an Agile coach?</span></div>
<br />
<div style="text-align: justify;">
<span style="font-family: "verdana" , sans-serif;"><br /></span></div>
<span style="font-family: "verdana" , sans-serif;"></span><br />
<div style="text-align: justify;">
<span style="font-family: "verdana" , sans-serif;">What is an Agile coach? When the question is asked to different people you’re sure to get different types of answers depending upon whom you’ve asked. The perception of <b><a href="https://www.quickscrum.com/Home/AgileCoaching" target="_blank">Agile coaching changes from individual to individual</a></b>, and from company to company. Perhaps the main reason why this happens is because there are no standard definitions explaining Agile coaching, and people have the liberty to interpret the terminology in a manner they deem correct.</span></div>
<span style="font-family: "verdana" , sans-serif;">
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
So, rather than trying to define exactly what an “Agile coach” is, it would be more worthwhile to comprehend what activities Agile coaching includes, and what does an Agile coach do when he/she is appointed by an organisation to facilitate or implement Scrum in their business processes. Coaching needs and activities vary from businesses to businesses based upon the type of product to be developed. However, in a typical organisation, there are three main areas where managements often decide Agile coaching is needed.</div>
<div style="text-align: justify;">
<br /></div>
<span style="font-size: large;"><div style="text-align: justify;">
Agile Team Facilitator</div>
</span><div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
An Agile facilitator may or may not possess a coaching certification from a reputed or known Scrum body. His/her primary role involves facilitating Scrum activities and mentoring Agile teams in achieving Scrum agility. The person usually engages with one or two Scrum teams – not more – and may lack experience or skill sets required for adopting and implementing Scrum to the fullest extent in the entire organisation.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Small organisations, or businesses having a limited Scrum budget but still interested in implementing Scrum may opt for Agile team facilitators to <b><a href="https://www.quickscrum.com/" target="_blank">introduce Scrum in their organisations</a></b> before deciding upon a concrete Scrum adoption plan. Usually, the objective of hiring an Agile team facilitator is to familiarise managements and development teams with the Scrum process and get an idea about how to go ahead with Scrum adoption, or, at times, to decide whether Scrum adoption is needed or not.</div>
<div style="text-align: justify;">
<br /></div>
<span style="font-size: large;"><div style="text-align: justify;">
Agile Coach</div>
</span><div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
An Agile coach can have one or more certifications from a well-known Scrum certification body. Unlike getting certified as a chartered account or a medical practitioner in a particular state or country, there are no formal or authorized “government recognized Scrum certification issuing authorities. Certification availed from a few Scrum entities like Scrum.Org, Scrum Alliance, Agile Coaching Institute, etc. carry value in the Scrum market, and employers generally search for coaches who have qualified or hold certifications from these type of institutes.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Agile coaches have a sound and relevant experience in at least one Agile discipline – Scrum, XP, or Kanban. They are certified Agile professionals who have achieved a high level of proficiency in their respective fields. They possess sufficient domain knowledge and coaching skills to facilitate and mentor the Scrum process in an organisation. An Agile coach trains the development team and the management in Agile principles and practices. He/she contributes at both macro and micro levels, and in addition resolves all Scrum related issues. Often, Agile coaches promote and act as Scrum ambassadors in organisations which appoint them.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Businesses appoint Agile and Scrum coaches when they decide to go “all the way” with Scrum, and want to make sure they benefit from Scrum principles. Coaches are also consulted to discuss ways and means to develop better products, increase the ROI, and improve the current business processes.</div>
<div style="text-align: justify;">
<br /></div>
<span style="font-size: large;"><div style="text-align: justify;">
Enterprise Agile Coach</div>
</span><div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
An Enterprise Agile coach is a person who has achieved some additional skills such as advanced systems coaching, understanding work culture, training organisations in specialized business processes, implementing change management, and creating collaboration and leadership qualities amongst individuals which “regular” Agile coaches may not possess.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
An <b><a href="https://www.quickscrum.com/Home/AgileTraining" target="_blank">Enterprise Agile coach may work at all levels</a></b> in an organisation and help managements in using Agile as a strategic asset for generating consistent and reliable business value by improving current processes through Agile.</div>
</span></div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0Clichy, France48.904526 2.304767999999967348.883651 2.2644274999999672 48.925400999999994 2.3451084999999674tag:blogger.com,1999:blog-651611792114842420.post-88238247740800647192014-10-28T02:51:00.001-07:002016-01-07T22:37:44.225-08:00Salient Features Of Scrum<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 style="text-align: justify;">
<span style="font-family: arial,helvetica,sans-serif;"><span style="font-size: 18px;">Agile - The base of Scrum</span></span></h2>
<div style="text-align: justify;">
<span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Agile,
and the path to Agility is now becoming a much sought after norm for
many businesses across the world. There is a huge demand for
understanding, and implementing, Agile based frameworks. Perhaps one of
the main reasons why Agile is becoming increasingly popular is because
consumer demands are changing radically and people now desire more. And,
people are not ready to wait. They want products which offer good value
for money, and that too with enhanced features. This has created a need
to develop products which are:</span></span></div>
<ul>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Competitive</span></span></li>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Feature rich</span></span></li>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Quickly available</span></span></li>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Fulfil specific end user requirements</span></span></li>
</ul>
<div style="text-align: justify;">
<span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Agile proposes to satisfy these requirements without adding on to the product costs.</span></span></div>
<div style="text-align: justify;">
<span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">The
basic issue with all Agile frameworks is that they are – frameworks.
They offer guidelines how the <b><a href="https://www.quickscrum.com/" target="_blank">Agile process can and should be implemented in a project</a></b>. For that, it becomes imperative to understand
what a framework is, and how it differs from a methodology. Many
individuals still feel Agile is a methodology and they could not be more
wrong.</span></span></div>
<h2 style="text-align: justify;">
<span style="font-size: 18px;"><span style="font-family: arial,helvetica,sans-serif;">Agile methodology misconception</span></span></h2>
<div style="text-align: justify;">
<span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">There
is still a misconception regarding Agile – some people still tend to
refer to <b><a href="https://www.quickscrum.com/Home/AgileMethodology" target="_blank">Agile as a methodology</a></b>. This is not true. A methodology offers a
set of rules, principles, tools, or practices that can be used to
conduct processes and achieve certain goals. A framework, on the other
hand, is a loose structure that leaves enough room for other tools and
practices to be included, and only provides the process required. In
simple terms, a methodology is like a doctor’s prescription – you have
to “take” it as per instructions provided, while a framework is like
trying out home remedies – you know what can be done to achieve a
particular objective, but it is up to you how to implement the remedy,
and when to implement it. An Agile framework has to be implemented in a
project to be successful, and there are no specific rules about how to
do it. You have to follow certain guidelines and configure your project
to function as per the rules specified in the framework. This is very
much the case with Agile. Agile is a framework.</span></span></div>
<h2 style="text-align: justify;">
<span style="font-size: 18px;"><span style="font-family: arial,helvetica,sans-serif;">Agile Scrum salient features</span></span></h2>
<div style="text-align: justify;">
<span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Of all Agile frameworks, Scrum and Extreme Programming “XP” are the most popular. Even though Scrum framework is more generally used for developing software projects,
it can also be used for developing non-IT projects. Scrum constitutes a
collection of ideas and rules pertaining to effective project
management. The framework supports collaboration and self-organisation.
The team members work jointly and develop the project. They collaborate
and share their ideas and findings. Scrum teams self-manage their
activities. The most important aspect of Scrum is that all activities
are time boxed. The client receives working versions of the product
features on a continued basis through product incremental cycles –
sprints – at regular intervals ranging from a week up to a maximum of
one month. Cycles keep on repeating until all product features are
developed and the product is ready. </span></span></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">A
unique aspect about <b><a href="https://www.quickscrum.com/Home/ScrumProjectManagement" target="_blank">Scrum is that the framework has a capability of adapting</a></b> itself to changing market conditions, and incorporates those
changes in the product development cycle even late during the
development process. The Scrum process focuses upon responding quickly
and efficiently to changing environments and assimilating those changes
in the product design. The client benefits though the development of a
product that is in tune with the most recent market demands. Moreover,
participation from the end users and incorporating their suggestions
while developing the product features further ensures that the product
developed is most likely to assume a high business value or worth. </span></span></div>
<ul>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Scrum - an agile process – focuses upon delivering high business values to the client in the shortest time possible.</span></span></li>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">It supports rapid and repeated inspection of the actual working software.</span></span></li>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">The product is developed in stages through the product incremental cycles known as sprints.</span></span></li>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">The client benefits from shippable product releases at the end of incremental cycle.</span></span></li>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Frequent and consistent product increments should be delivered to the client.</span></span></li>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">The client, and the business, sets the priority.</span></span></li>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">The
working process responds quickly and efficiently to the changes
occurring in the market conditions, and in incorporating those changes
into the product features in the least time possible.</span></span></li>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Scrum teams self-organise and self-manage to determine the most efficient and quick way of delivering high priority features.</span></span></li>
</ul>
<h2 style="text-align: justify;">
<span style="font-size: 18px;"><span style="font-family: arial,helvetica,sans-serif;">Scrum principles</span></span></h2>
<div style="text-align: justify;">
<span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Scrum functions as per certain rules or principles which are very important for its efficient working:</span></span></div>
<table align="left" border="0" cellpadding="0" cellspacing="1" style="width: 410px;"><tbody>
<tr>
<td><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Individuals and interactions</span></span></td>
<td><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">over</span></span></td>
<td><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Process and tools</span></span></td>
</tr>
<tr>
<td><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Working software</span></span></td>
<td><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">over</span></span></td>
<td><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Comprehensive documentation</span></span></td>
</tr>
<tr>
<td><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Customer collaboration</span></span></td>
<td><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">over</span></span></td>
<td><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Contract negotiation</span></span></td>
</tr>
<tr>
<td><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Responding to change</span></span></td>
<td><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">over</span></span></td>
<td><span style="font-size: 14px;"><span style="font-family: arial,helvetica,sans-serif;">Following a plan</span></span></td></tr>
</tbody></table>
</div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-58151249872136728222014-10-21T03:55:00.000-07:002016-01-07T22:43:52.990-08:00Breaking Down The Agile Manifesto And Understanding It<div dir="ltr" style="text-align: left;" trbidi="on">
<div class="article-text">
<span style="font-family: Verdana,sans-serif;">The popularity of Agile frameworks, especially XP and Scrum,
is increasing by the day, and more and more organisations are deciding
in favour of using these frameworks to execute their projects. Agile
proposes many advantages – frequent and reliable product increments,
delivering product features having high business values, and above all –
delivery of shippable product features even while the development
process is underway. However, a major issue with Agile, and all Agile
based frameworks is that the framework has to be properly understood and
later implemented in the project. Moreover, the implementation should
be carried out keeping Agile principles in mind. More than often,
businesses fail to benefit from Agile simply because the management has
not understood the basic principles behind the framework, or has failed
to implement those principles in a proper manner.</span></div>
<div class="article-text">
<br /></div>
<span style="font-family: Verdana,sans-serif;">
</span><h2 class="article-title2">
<span style="font-family: Verdana,sans-serif;"><a class="link-hover" dir="ltr" href="http://www.agilealliance.org/the-alliance/the-agile-manifesto/" target="_blank"> The Agile manifesto</a></span></h2>
<span style="font-family: Verdana,sans-serif;">
</span><div class="article-text">
<span style="font-family: Verdana,sans-serif;">Since it was developed in 2001, thousands of
individuals including project managers, software professionals, and C
level executives have endorsed the Agile manifesto. Hundreds of books
and references have been written to discuss what the guide has to say,
and how it should be interpreted. The manifesto has drastically changed
the way in which organisations and individuals develop software
projects. The manifesto packs a lot of punch for its 68 words which have
been written by 17 software professionals over a two days meet at a ski
resort.</span></div>
<div class="article-text">
<br /></div>
<span style="font-family: Verdana,sans-serif;">
</span><div class="article-text">
<span style="font-family: Verdana,sans-serif;"> The principles of Agile are stated in the
official guide written by Ken Schwaber and Jeff Sutherland. The guide
functions as a bible for all Agile groups and Agile professionals.
People refer to the guide when in doubt, or when they wish to clarify a
particular point during Agile framework implementation. For individuals
interested in Agile, it is very important to understand the guide and
interpret what it has to say.</span></div>
<div class="article-text">
<br /></div>
<div style="text-align: center;">
<span style="font-family: Verdana,sans-serif;">
<span class="article-title2"> <a class="link-hover" href="http://www.agilealliance.org/the-alliance/the-agile-manifesto/" target="_blank"> Manifesto for Agile Software Development</a></span>
</span></div>
<div class="article-text" style="text-align: center;">
<br /></div>
<div class="article-text" style="text-align: center;">
<span style="font-family: Verdana,sans-serif;">We are uncovering better ways of developing software by doing it and helping others do it.</span></div>
<div style="text-align: center;">
<span style="font-family: Verdana,sans-serif;">
</span></div>
<div class="article-text" style="text-align: center;">
<span style="font-family: Verdana,sans-serif;">Through this work we have come to value:</span></div>
<div style="text-align: center;">
<span style="font-family: Verdana,sans-serif;">
</span></div>
<div class="article-text" style="text-align: center;">
<span style="font-family: Verdana,sans-serif;">
Working software over comprehensive documentation<br />
Customer collaboration over contract negotiation<br />
Responding to change over following a plan</span></div>
<div style="text-align: center;">
<span style="font-family: Verdana,sans-serif;">
</span></div>
<div class="article-text" style="text-align: center;">
<span style="font-family: Verdana,sans-serif;">That is, while there is value in the items on the right, we value the items on the left more.</span></div>
<span style="font-family: Verdana,sans-serif;">
<span class="article-title2"> </span></span><br />
<span style="font-family: Verdana,sans-serif;"><b><span class="article-title2">We</span></b>
</span><br />
<div class="article-text">
<span style="font-family: Verdana,sans-serif;">To start with, the manifesto states “We” i.e. it
emphasis that Agile is not a solo endeavour. It involves group activity
and people have to collaborate while working, at every level, and at
every instant. Development teams, project teams, and organisation have
to work jointly as a composite unit, and rely upon each other for
completing work.</span></div>
<span style="font-family: Verdana,sans-serif;">
<span class="article-title2"> </span></span><br />
<span style="font-family: Verdana,sans-serif;"><b><span class="article-title2">are uncovering</span></b> </span><br />
<span style="font-family: Verdana,sans-serif;">Here, the guide suggests that Agile does not
offer one-size-fits-all type of solutions. Agile cannot be standardised
and implemented in a project. People involved with Agile processes have
to put in efforts, and strive to seek answers through discussions and
collaborations. Answers have to be discovered through experimentation,
and the “adapt” and “inspect” principles which are... <b><a href="https://www.quickscrum.com/Article/ArticleDetails/4075/3/Breaking-Down-The-Agile-Manifesto-And-Understanding-It" target="_blank">Read more</a></b></span></div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-38932684802403708752014-10-10T05:07:00.000-07:002015-11-24T02:24:53.894-08:00Scrum Product Owner Role And Sprint Planning Meeting Agenda<div dir="ltr" style="text-align: left;" trbidi="on">
<div class="MsoNormal">
<span style="font-family: "verdana" , sans-serif;"><span style="color: #4b4c4d; font-family: "trebuchet ms" , "sans-serif"; font-size: 10.5pt; mso-bidi-font-family: Arial; mso-fareast-font-family: "Times New Roman";">In many ways, in a Scrum project, the</span><span style="color: #4b4c4d; font-family: "trebuchet ms" , "sans-serif"; font-size: 10.5pt; mso-bidi-font-family: Arial; mso-bidi-font-size: 11.0pt; mso-fareast-font-family: "Times New Roman";"> <b><a href="https://www.quickscrum.com/Kernel/Tools/sprint-planning.aspx" target="_blank"><span style="color: blue;">sprint planning meeting agenda</span></a></b> </span><span style="color: #4b4c4d; font-family: "trebuchet ms" , "sans-serif"; font-size: 10.5pt; mso-bidi-font-family: Arial; mso-fareast-font-family: "Times New Roman";">plays a very
significant part in determining the success of delivering shippable product
increments through the sprint iterative cycles. The product owner is very
closely involved in the sprint planning agenda, and is responsible for the
outcome of the sprint cycle, since he or she is primarily responsible for
taking the initiative and “designing” the sprint – the PO decides which user
stories should be ideally taken up for development purposes based upon their
business values. Moreover, the product backlog needs to be refined on a regular
basis. The PO may invite and seek the help of Agile team members to keep the
backlog refined so “granular” and developable user stories are available at the
time of Scrum planning meeting.</span><span style="color: #4b4c4d; font-family: "arial" , "sans-serif"; font-size: 10.5pt; mso-fareast-font-family: "Times New Roman";"><o:p></o:p></span></span></div>
<div class="MsoNormal">
<span style="font-family: "verdana" , sans-serif;"><span style="color: #4b4c4d; font-family: "trebuchet ms" , "sans-serif"; font-size: 10.5pt; mso-bidi-font-family: Arial; mso-fareast-font-family: "Times New Roman";">The main issue with Agile Scrum today is that the role of a PO
cannot be “standardised” based upon assumptions as to how Scrum ought to be
implemented in a project, and what the PO should ideally do to make the project
a distinct success. In addition, while considering Scrum sprint planning, the
same thoughts might be applicable to it as those associated with the PO’s – it
is difficult to create generalised rules regarding how a sprint should be
ideally designed. The primary reason is products and requirements change as per
fluctuating market conditions, and stakeholders too are liable to change their
thoughts as and when end user demand user-specific requirements and
development. However, after considering the fact that scaled Scrum versions are
likely to “dominate” the Agile scenario over the coming years, it is worthwhile
thinking that “some” of the duties of a PO and certain sprint planning
“characteristics” are likely to remain common – irrespective of which scaled
version is used, and the manner in which Scrum should be, or can be, implemented
in a project. In addition, while the sprint planning meeting was traditionally
conducted in two parts, the Scrum event has now evolved to be conducted as a
whole – as a single event – and include two topics in it, rather than two
parts:</span><span style="color: #4b4c4d; font-family: "arial" , "sans-serif"; font-size: 10.5pt; mso-fareast-font-family: "Times New Roman";"><o:p></o:p></span></span></div>
<ul type="disc">
<li class="MsoNormal" style="color: #555555;"><span style="font-family: "verdana" , sans-serif;"><span style="font-family: "trebuchet ms" , "sans-serif"; font-size: 10.5pt; mso-bidi-font-family: Arial; mso-fareast-font-family: "Times New Roman";">What
can be done in this (currently being planned) sprint – the “What” aspect</span><span style="font-family: "arial" , "sans-serif"; font-size: 10.0pt; mso-fareast-font-family: "Times New Roman";"><o:p></o:p></span></span></li>
<li class="MsoNormal" style="color: #555555;"><span style="font-family: "verdana" , sans-serif;"><span style="font-family: "trebuchet ms" , "sans-serif"; font-size: 10.5pt; mso-bidi-font-family: Arial; mso-fareast-font-family: "Times New Roman";">How
should the chosen “work” be ideally “done” – the “How” aspect</span><span style="font-family: "arial" , "sans-serif"; font-size: 10.0pt; mso-fareast-font-family: "Times New Roman";"><o:p></o:p></span></span></li>
</ul>
<div class="MsoNormal">
<span style="font-family: "verdana" , sans-serif;"><span style="color: #4b4c4d; font-family: "trebuchet ms" , "sans-serif"; font-size: 10.5pt; line-height: 115%; mso-bidi-font-family: Arial; mso-fareast-font-family: "Times New Roman";">It is interesting to think about</span><span style="color: #4b4c4d; font-family: "trebuchet ms" , "sans-serif"; font-size: 10.5pt; line-height: 115%; mso-bidi-font-family: Arial; mso-bidi-font-size: 11.0pt; mso-fareast-font-family: "Times New Roman";"> <b><a href="https://www.quickscrum.com/" target="_blank"><span style="color: blue;">how the product owner’s role is likely to modify</span></a></b> </span><span style="color: #4b4c4d; font-family: "trebuchet ms" , "sans-serif"; font-size: 10.5pt; line-height: 115%; mso-bidi-font-family: Arial; mso-fareast-font-family: "Times New Roman";">itself in the future, and what features the sprint planning
event is likely to include. The suggestions are open for debate, and the reader
is invited to present his or her viewpoints.<o:p></o:p></span></span></div>
<h2>
<span style="font-family: "verdana" , sans-serif;"><span style="color: #333333; font-family: "trebuchet ms" , "sans-serif"; font-size: 15.0pt; font-weight: normal; line-height: 115%; mso-bidi-font-family: Arial;">Scrum product
owner role and responsibilities likely to remain “common”</span><span style="color: #333333; font-family: "arial" , "sans-serif"; font-size: 18.0pt; font-weight: normal; line-height: 115%;"><o:p></o:p></span></span></h2>
<ul type="disc">
<li class="MsoNormal" style="color: #555555;"><span style="font-family: "verdana" , sans-serif;"><span style="font-family: "trebuchet ms" , "sans-serif"; font-size: 10.5pt; mso-bidi-font-family: Arial;">Creation of the product backlog based upon the
vision as seen by the stakeholders. Defining user stories having high
business values so the project “worth” is maintained at all times.</span><span style="font-family: "arial" , "sans-serif"; font-size: 10.0pt;"><o:p></o:p></span></span></li>
<li class="MsoNormal"><span style="color: #555555; font-family: "verdana" , sans-serif;"><span style="font-size: 10.5pt;">Monitoring all Scrum related activities in
project. Even if the PO’s role may be demanding and “difficult to play”,
the PO still has to deal with changing market conditions, stakeholders
requests, and negotiate with the development team with regards delivering
shippable stories and maintaining team velocity... Read more at </span><span style="font-size: 14px;"><a href="https://www.quickscrum.com/Article/articledetails/2017/1/Scrum-Product-Owner-Role-And-Sprint-Planning-Meeting-Agenda/" target="_blank"><b>Scrum Product Owner Role And Sprint Planning Meeting Agenda</b></a></span></span></li>
</ul>
<div>
<span style="font-family: "verdana" , sans-serif;"><br /></span></div>
<div>
<span style="color: #555555; font-family: "trebuchet ms" , sans-serif;"><span style="font-family: "verdana" , sans-serif; font-size: 14px;"><br /></span></span></div>
<div>
<br /></div>
</div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-90009265211948113222014-10-07T06:52:00.000-07:002015-11-24T02:52:29.973-08:00Scrum Product Owner’s Role<div dir="ltr" style="text-align: left;" trbidi="on">
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<span lang="EN-IN" style="font-family: Verdana, sans-serif; font-size: 10.0pt; mso-bidi-font-family: Calibri;">Agile professionals have often discussed what the
exact role of a product owner should be in Scrum. What virtues should a product
owner possess to be considered a “good” PO? The answers are many. And this is
not surprising because Scrum is a framework, and its implementation in a
project depends upon the requirements specific to the project. When
requirements change, the role of the PO also changes. Therefore, it may not be
possible to standardise the exact role a PO should play in a Scrum project. <o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<span style="font-family: Verdana, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<span lang="EN-IN" style="font-family: Verdana, sans-serif; font-size: 10.0pt; mso-bidi-font-family: Calibri;">A certain process flow remains common to almost
all Scrum projects. The role of a product owner can be thought about in terms
of what POs actually do in a typical Scrum project. Here are a few suggestions:<o:p></o:p></span></div>
<div style="text-align: justify;">
<span style="font-family: Verdana, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<span style="font-family: Verdana, sans-serif;"><br /></span></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="http://www.quickscrum.com/" target="_blank"><span style="font-family: Verdana, sans-serif;"><img alt=" Scrum Tool" border="0" height="211" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgXSb8v4qJhldIqqUa2xbwEdNbchjzeHUCANBoLy-sBNKDk66nlK9kxpuyE9hh8BgU1QX6lrRfYH-3qBJK4OUXBt5bzkbZYLy2LC7nLJG5W7f3YYkVhXljVOMr1s9k8EhBM9EuWpvMo2Mg9/s1600/img_product_owner.png" width="320" /></span></a></div>
<div class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.2in;">
<div style="text-align: justify;">
<b><span lang="EN-IN" style="font-family: Verdana, sans-serif; font-size: 12.0pt; mso-bidi-font-family: Calibri;">Common role or activities of a <a href="https://www.quickscrum.com/" target="_blank">Scrum product owner</a>
</span></b></div>
</div>
<div style="text-align: justify;">
<span style="font-family: Verdana, sans-serif;"><br /></span></div>
<div class="Bulletnormal" style="margin-left: .4in; tab-stops: list .2in;">
<div style="text-align: justify;">
<!--[if !supportLists]--><span style="font-family: Verdana, sans-serif;"><span lang="EN-IN" style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;">· </span><span lang="EN-IN">Creating the product backlog as
per the product vision seen by the stakeholders. Defining user stories having
high business values in the backlog so the project “value” is constantly
maintained. </span></span></div>
</div>
<div class="Bulletnormal" style="margin-left: .4in; tab-stops: list .2in;">
<div style="text-align: justify;">
<!--[if !supportLists]--><span style="font-family: Verdana, sans-serif;"><span lang="EN-IN" style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;">· </span><span lang="EN-IN">Monitoring and tracking all
Scrum activities. The role of a product owner may be difficult to act since a
project might be demanding, and the product owner may have to cater to market
related issues and still monitor the work carried out by the team. Balancing
both the aspects can prove to be trying.</span></span></div>
</div>
<div class="Bulletnormal" style="margin-left: .4in; tab-stops: list .2in;">
<div style="text-align: justify;">
<!--[if !supportLists]--><span style="font-family: Verdana, sans-serif;"><span lang="EN-IN" style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;">· </span><span lang="EN-IN">Make sure that the product
backlog is kept refined at all times. Moreover, the product backlog should be
accessible by the entire team. </span></span></div>
</div>
<div class="Bulletnormal" style="margin-left: .4in; tab-stops: list .2in;">
<div style="text-align: justify;">
<!--[if !supportLists]--><span style="font-family: Verdana, sans-serif;"><span lang="EN-IN" style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;">· </span><span lang="EN-IN">Each product backlog item “PBI”
should be properly stated and defined in the product backlog. The story
description, appropriate business value, and the acceptance criteria should be
stated precisely in the story card and explained to the entire team so the team
members can develop effective stories and develop shippable product features. </span></span></div>
</div>
<div class="Bulletnormal" style="margin-left: .4in; tab-stops: list .2in;">
<div style="text-align: justify;">
<!--[if !supportLists]--><span style="font-family: Verdana, sans-serif;"><span lang="EN-IN" style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;">· </span><span lang="EN-IN">To be available whenever
needed, to remain present, and share information, knowledge, as well as
expertise with other team members.</span></span></div>
</div>
<div class="Bulletnormal" style="margin-left: .4in; tab-stops: list .2in;">
<div style="text-align: justify;">
<!--[if !supportLists]--><span style="font-family: Verdana, sans-serif;"><span lang="EN-IN" style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;">· </span><span lang="EN-IN">The PO responsibility should
also include defining productive sprint goals just before a sprint commences.</span></span></div>
</div>
<div class="Bulletnormal" style="margin-left: .4in; tab-stops: list .2in;">
<div style="text-align: justify;">
<!--[if !supportLists]--><span style="font-family: Verdana, sans-serif;"><span lang="EN-IN" style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;">· </span><span lang="EN-IN">A product owner’s
responsibility should also include... Read more at </span></span><span style="text-align: left;"><span style="font-family: Verdana, sans-serif;"><a href="https://www.quickscrum.com/Article/articledetails/2016/1/Scrum-Product-Owner-Role/" target="_blank"><b>Scrum Product Owner's Role</b></a></span></span></div>
</div>
<!--[if gte vml 1]><v:shapetype id="_x0000_t75"
coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe"
filled="f" stroked="f">
<v:stroke joinstyle="miter"/>
<v:formulas>
<v:f eqn="if lineDrawn pixelLineWidth 0"/>
<v:f eqn="sum @0 1 0"/>
<v:f eqn="sum 0 0 @1"/>
<v:f eqn="prod @2 1 2"/>
<v:f eqn="prod @3 21600 pixelWidth"/>
<v:f eqn="prod @3 21600 pixelHeight"/>
<v:f eqn="sum @0 0 1"/>
<v:f eqn="prod @6 1 2"/>
<v:f eqn="prod @7 21600 pixelWidth"/>
<v:f eqn="sum @8 21600 0"/>
<v:f eqn="prod @7 21600 pixelHeight"/>
<v:f eqn="sum @10 21600 0"/>
</v:formulas>
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/>
<o:lock v:ext="edit" aspectratio="t"/>
</v:shapetype><v:shape id="_x0000_s1028" type="#_x0000_t75" style='position:absolute;
margin-left:-4.65pt;margin-top:196.7pt;width:500.9pt;height:331.5pt;z-index:251658240;
mso-wrap-distance-left:9.05pt;mso-wrap-distance-right:9.05pt;
mso-position-horizontal:absolute;mso-position-horizontal-relative:text;
mso-position-vertical:absolute;mso-position-vertical-relative:text' filled="t">
<v:fill opacity="0" color2="black"/>
<v:imagedata src="file:///C:\Users\sengi\AppData\Local\Temp\msohtmlclip1\01\clip_image001.png"
o:title=""/>
<w:wrap type="square"/>
</v:shape><![endif]--><!--[if !vml]--><!--[endif]--></div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-61584850104217214302014-10-01T06:19:00.000-07:002014-10-10T05:05:05.178-07:00What is Role of Scrum Product Owner?<div dir="ltr" style="text-align: left;" trbidi="on">
Several discussions have been carried out by Agile professionals regarding the Scrum product owner role. What virtues make a product owner an “ideal” one? How should a PO delegate authority? Should it be as per traditional management models, or should a servant-leader role be employed? How should the person handle stakeholders when there are issues? There are many questions. The debate can keep on extending indefinitely since newer “scaled” versions of Scrum keep on coming, and the PO has to change his or her role based upon the traditional, or scaled, version of Scrum the management decides to follow.<br />
<br />
It would be more practical to concentrate upon some of the most important, and the most common, activities of a PO.<br />
<br />
<img alt="Scrum Product Owner Role" src="http://www.quickscrum.com/Images/Article/img_product_owner.png" height="211" width="320" /><br />
<br />
<table id="tblArticle" style="background-color: white; color: #555555; font-family: Arial, Helvetica, sans-serif; font-size: 13px; padding-top: 20px; width: 100%px;"><tbody>
<tr id="trTraining_3"><td align="left" class="wordwrap" id="tdArticleDetail_19" style="display: inline-block; width: 940.5px; word-wrap: break-word;"><h2 style="text-align: justify;">
<span style="color: #333333; font-family: trebuchet ms, helvetica, sans-serif; font-size: small;"><span style="font-weight: normal;">Read more at </span></span></h2>
<h2 style="text-align: justify;">
<span style="color: #333333; font-family: trebuchet ms, helvetica, sans-serif; font-size: small;"><a href="http://www.quickscrum.com/Kernel/Article/frmArticleDetails.aspx?PAGE_TITLE=Scrum%20Product%20Owner%20Role&ARTICLE_ID=2016" target="_blank">Scrum Product Owner Role</a></span></h2>
</td></tr>
</tbody></table>
</div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-69817642719738880772014-10-01T05:50:00.000-07:002014-10-01T05:50:36.195-07:00What is Sprint planning meeting agenda?<div dir="ltr" style="text-align: left;" trbidi="on">
<br />
In a Scrum project, the Sprint planning meeting agenda is one of the most important activities undertaken by the team. The product owner plays an important part in the agenda. In Scrum, out of the many important duties carried out by a PO, a very important one is to create the product backlog based upon the vision of the stakeholders, and subsequently maintain or “groom” it with the help of team members (preferably). However, once the backlog is created and all required product backlog items are properly defined in it, it becomes necessary to “prepare” for the next step in the Agile product development cycle – plan and develop effective sprints so shippable user stories are delivered at the end of sprint cycles. Offering consistent development over successive sprint iterations is an inherent feature of Agile Scrum. In a sprint planning agenda, the objective of a sprint meeting is to prepare productive sprints so the team can develop meaningful stories.<br />
<br />
So, what does a sprint planning meeting actually consist of? In practice, the meeting is conducted in two parts – the first part is dominated by the product owner while in the second part the development team actually prepares tasks from user stories taken up for development in the sprint backlog.<br />
<br />
<b>1st part of sprint planning</b><br />
<br />
The product owner is the most “conversant” person as far as user stories are concerned since he or she actually “creates” the product backlog. The stories need to be explained to the team members. During the first part of the Scrum sprint planning meeting, the PO selects some of the most important product backlog items from the top of the backlog, and creates a “sprint backlog” by transferring the selected stories into it. So, the sprint backlog is a subset of the main backlog, and contains a “chunk” of stories which carry high business values. The PO explains how the development of a particular story should be carried out by the development team. The acceptance criteria is explained and the team is briefed regarding what it should do to ensure their “development” is shippable i.e. the stories are bug free and satisfy the benchmarks or acceptance criteria linked with each story. The PO also answers any doubts or queries put up by the team.<br />
<br />
<img alt="Sprint Planning Meeting Agenda" src="http://www.quickscrum.com/Images/Article/img_productbacklog.png" /><br />
<br />
The first part is attended by the entire team – the product owner, scrum master, and the development team members. It is not necessary for the stakeholders and project owners to attend the meeting, but if they desire to do so, they can attend the meeting as “passive” invitees, and not disturb the proceedings with their suggestions or even try to get “involved” in the meeting.<br />
<br />
<b>2nd part of sprint planning</b><br />
<br />
User stories form the base of all development activity in Scrum. The entire product is developed by creating shippable stories, which are later integrated to “form” the complete product. During the second part of the Scrum planning meeting, the team starts discussing how it will carry out the actual development activity and create the stories in the sprint backlog. Generally, a Scrum team is “multi-talented” i.e. each team member possesses more than one type of expertise. However, it is important to know that this may not always be the case in all Scrum projects, since the product requirements and resources may vary depending upon the nature of product to be developed. <br />
<br />
The team members – developers, programmers, designers, QA personnel, and technical writers – decide amongst themselves how the user stories should be split up into parts that are more “manageable”. Each such “part” is referred to as a “task” in Scrum. Tasks are developed to create shippable user stories. A developer can develop each task individually. Certain Scrum teams may even work in “pairs”. Members collaborate, and decide amongst themselves as to who should take up which task depending upon the experience and levels of expertise possessed by them. Once the tasks are “distributed” the actual sprint can begin.Read more at<br />
<h1 style="background-color: white; color: #27568e; font-family: Arial, Helvetica, sans-serif; font-size: 18px;">
<a href="http://www.quickscrum.com/Kernel/Article/frmArticleDetails.aspx?PAGE_TITLE=Sprint%20planning%20meeting%20agenda&ARTICLE_ID=2012" target="_blank">Sprint planning meeting agenda</a></h1>
</div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-7147328248176869712014-10-01T05:44:00.000-07:002014-10-01T05:44:51.741-07:00Why Agile Can Be A Popular Software Development Framework?<div dir="ltr" style="text-align: left;" trbidi="on">
Software products penetrate almost every aspect of human existence today. They manifest themselves in a multitude of manner, and remain omnipresent in a host of devices ranging from washing machines and smartphones to automobiles and computers. Owing to a consistent usage of different types of digital devices by people across the world, software applications and utilities have to evolve as and when consumer requirements change and “strive” to fulfil the new set of requirements demanded by end users. It is, therefore, essential to develop newer versions of existing software products more frequently, in the shortest time possible, and in a manner such that end users do not face any problems while using the products in the upcoming months. Stiff market competitions and an ever-increasing consumer “appetite” for feature-rich products have created a special need to implement a reliable and sustainable product development methodology, or a framework, which can aid in developing sophisticated software products in a relatively short time. Moreover, the methodology should also help in reducing the developmental overheads so investment returns can be increased. As on today, a reliable project development methodology is very much required to fulfil the business goals on a consistent basis, and earn large profits from the products manufactured by IT companies. <br />
<br />
Over the decades, IT stalwarts have introduced many software development frameworks and project management methodologies. While many of these methodologies have proved to be useless and non-productive, a large number of them have been, in fact, successful in delivering the desired results – with varying levels of acceptance. With the passage of time, two software development frameworks have managed to dominate the field of software development. The frameworks are:<br />
<br />
<b>1. Waterfall</b><br />
It is a traditional software development framework typically featuring “staged” development processes which have to be “carried out” one after the other. A unique aspect about this framework is that product development starts from the “topmost” stage and “flows” towards the “bottommost” stage. Once started, the product development cycle cannot reverse itself – it is unidirectional in nature. The framework is widely used, and is very popular amongst software development companies, primarily because the framework has “been around” for a long time and used by a large number of software developers and IT firms. It is easy to understand and use. Therefore, it is also used for teaching the software development process to engineering students. Even though it is a much sought after development framework, a large number of individuals and companies traditionally using Waterfall methods for developing their software products are now finding it increasingly difficult to meet the changing global software trends, and developing state-of-the-art applications and utilities, which are so much in vogue today.<br />
<br />
<br />
<b>2. Agile</b><br />
A comparatively new “entrant” Agile has managed to find a special niche for itself in the IT development field over the years. The Agile framework was originally envisioned, and developed, to overcome the defects of traditional software project management methodologies and frameworks, which had failed to evolve “in the desired direction”, could not adapt themselves to the changing market trends, and offer reduced turnaround times. There are many reasons why “lightweight” Agile frameworks have become popular development platforms:<br />
<br />
They support product development through “short bursts” of programming/development activity, generally lasting from two weeks up to one month. It is much easier to develop, test, and document smaller “pieces” of code, features, and functionality rather than entire projects. Individually developed features are later integrated to form the “complete” product. The frameworks primarily focus upon rapid delivery of “shippable” products and business value.<br />
The client is actively involved with the team and the development process. Each feature is checked and “cleared” by the stakeholders before it is accepted as “Done”. This leads to increased customer satisfaction and enhanced user experience.<br />
Potential pitfalls are identified well in advance, at a micro level, so it is much easier to control regression and reduce technical debt. Agile software projects generally help to earn good profit margins.<br />
Agile frameworks support error detection and error correction processes. Technical errors are discovered early during the product development process, and dealt with effectively.<br />
The frameworks provides an opportunity to carry out “retrospective” thinking, reflect in terms of where the project is heading, and what “more” could be done to improve the product development process.<br />
<br />
<strong style="background-color: white; color: #4b4c4d; font-family: 'trebuchet ms', helvetica, sans-serif; text-align: justify;"><big>Agile and the scope of software development</big></strong><br style="background-color: white; color: #4b4c4d; font-family: 'trebuchet ms', helvetica, sans-serif; margin: 0px; text-align: justify;" /><span style="background-color: white; color: #4b4c4d; font-family: 'trebuchet ms', helvetica, sans-serif; text-align: justify;">Individuals associated with the software industry generally prefer using the term “software development”</span><span style="background-color: white; color: #4b4c4d; font-family: 'trebuchet ms', helvetica, sans-serif; text-align: justify;"> Read more at </span><span style="color: #4b4c4d; font-family: trebuchet ms, helvetica, sans-serif;"><a href="http://www.quickscrum.com/Kernel/Article/frmArticleDetails.aspx?PAGE_TITLE=Why%20Agile%20Can%20Be%20A%20Popular%20Software%20Development%20Framework&ARTICLE_ID=2003" target="_blank">Why Agile Can Be A Popular Software Development Framework?</a></span><br />
</div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-23130787266642675222014-09-30T02:04:00.000-07:002014-09-30T02:04:05.354-07:00Which Software Development Activities famous In The IT Field?<div dir="ltr" style="text-align: left;" trbidi="on">
Individuals who are associated with the IT industry and computers generally use the term “software development” to describe the particular kind of work, or activity, they are currently doing or involved with. The terminology is very loosely used by most people, and can include almost any type of computer programming activity - including testing, debugging, document creation, deployment, developing and maintaining application frameworks, and even customising operating systems as well as platforms. There is a trend to mention one’s profession, or one’s mode of professional engagement as “software development” while the person may be working as an application developer, a Java or VBScript web developer, an Android or iOS mobile apps creator, or even developing scripts for WordPress based themes.<br />
<br />
The fact is, the words “software development”are extensively used to refer to almost any type of IT related work, or activity, and generally denotes a development of “computerizable” code, in any way or manner, and of any “kind”. The following list provides a rough idea regarding the scope of development related activities in the IT field.<br />
<br />
The list is periodically updated and keeps on evolving to include the new scope of software development.<br />
<br />
Current list updated on 29th July, 2014.<br />
<br />
<b>Languages and scripts</b><br />
Scripts and scripting languages:<br />
<br />
HTML / HTML5 / DHTML / XHTML<br />
Active Server Pages - ASP<br />
VBScript<br />
JScript and JavaScript<br />
Personal Home Page - PHP<br />
ColdFusion ( ColdFusion Markup Language - CFML)<br />
Ajax<br />
Ruby (Ruby on Rails)<br />
Python<br />
AppleScript<br />
TypeScript<br />
Job Control Language - JCL<br />
Unix Shell scripts - ksh, csh, bash, sh, and others<br />
<br />
<b>Assembly languages:</b><br />
<br />
Autocoder (used for programming mainframe systems such as IBM 1401 and 1440)<br />
BAL (Basic AssembLer used for coding IBM System/360 and other mainframe systems)<br />
FAP (Fortran Assembly Program for encoding IBM mainframes 709, 7090, and 7094)<br />
GAS (acronym for GNU Assembler)<br />
HLA (acronym for High Level Assembly)<br />
MASM (acronym for Microsoft Macro Assembler)<br />
MI (acronym for Machine Interface)<br />
Motorola 68k Assembly (used for encoding Motorola 68000 family CPUs)<br />
NASM (acronym for Netwide Assembler)<br />
PASM<br />
TASM (Turbo Assembler developed by Borland)<br />
<br />
<b>Authoring languages:</b><br />
<br />
PILOT<br />
Command line interface languages:<br />
<br />
4DOS (extended command line shell for IBM PC family)<br />
csh and tcsh (C-like shell developed by Bill Joy while at UC Berkeley)<br />
CLIST<br />
DCL DIGITAL Command Language (for DEC, Compaq, HP)<br />
DOS batch language (standard batch language for IBM PCs and clones running under MS-DOS, PC DOS, and DR-DOS before Windows)<br />
EXEC 2<br />
JCL (punch card oriented batch language used in IBM Systems and 360 family mainframes)<br />
REXX<br />
TACL (acronym for Tandem Advanced Command Language)<br />
Windows batch language (as understood by COMMAND.COM and used by accessing the Command Prompt)<br />
Windows PowerShell<br />
<br />
<b>Compiled languages:</b><br />
<br />
Ada<br />
ALGOL<br />
BASIC<br />
C<br />
C++<br />
CLIPPER 5.3<br />
C#<br />
COBOL<br />
Cobra<br />
Common Lisp<br />
Delphi<br />
Fortran<br />
Pascal<br />
Visual Basic<br />
Visual FoxPro<br />
Visual Prolog<br />
<br />
<b>Educational languages:</b><br />
<br />
Alice<br />
Logo<br />
<br />
<b>Mobile operating systems and applications development</b><br />
<br />
Android<br />
Symbian<br />
Apple iOS<br />
Blackberry OS<br />
Windows OS<br />
Palm OS<br />
<br />
<b>Portals and websites</b><br />
<b>Web portals</b><br />
Early types of portals, which originated, and are still being developed, ever since the World Wide Web or the internet started becoming popular amongst the masses. These portals and websites exhibit assimilated content, and typically display links supporting searching facilities.<br />
<br />
<b>E-commerce portals</b><br />
E-commerce portals, also known as e-business portals help to share information with customers, partners, and suppliers. They generally support an online payment gateway or an “online transactions” processing component. The portals provide information, and in addition describe products and services. E-commerce portals try to increase customer-relationships and lower the product/service costs.<br />
<br />
<b>Self-service portals</b><br />
These portals target employees, suppliers, and/or customers, and allow access to information which can aid the users in carrying out specific processes and activities.<br />
<br />
<b>Business intelligence portals</b><br />
Also known as decision portals, business intelligence portals aid online users in making important decisions. Besides allowing users to submit query and avail reports across multiple data storages, business intelligence portals have many built-in facilities and tools that can help to generate targeted reports.<br />
<br />
<b>Collaboration portals</b><br />
These types of portals provide information pertaining to geographically dispersed workforces, and help to interact with people and projects sharing a common cause or belief. Typically, collaboration portals provide generic tools supporting chat and white boards, in addition to threaded discussions and streams which help to share maps and documents.<br />
<br />
<b>Enterprise information portal</b><br />
Generally of complex nature, enterprise information portals are highly tailored, and offer a unique experience to the visitors. Various legacy systems offer functionality to carry out predefined business related processes.<br />
<br />
<b>e-learning portals</b><br />
Supporting online education, e-Learning portals aim to help and guide students by offering an organised and structured learning experience. These portals also offer testing facilities to evaluate your learning, and provide appropriate feedback to the students.<br />
<br />
<b>Communication portals</b><br />
Communication portals, as the name rightly suggests, fundamentally support communications and messaging facilities through emails, voice messages, mobile linkups, web feeds, etc. in a manner that allows access from across multiple interfaces and locations. The users can configure how to use the facilities.<br />
<br />
<b>Social networking portals</b><br />
These types of portals can be individual or groups based, and primarily aim to improve and enhance social communications between like-minded individuals, or those who share a common idea or belief. Typically, members subscribe and log into the portal and subsequently start sharing their ideas and thoughts with other member groups and individuals.<br />
source:-<br />
<h1 style="background-color: white; color: #27568e; font-family: Arial, Helvetica, sans-serif; font-size: 18px;">
<a href="http://www.quickscrum.com/Kernel/Article/frmArticleDetails.aspx?PAGE_TITLE=Software%20Development%20Activities%20In%20The%20IT%20Field&ARTICLE_ID=1003" target="_blank">software Development Activities In The IT Field</a></h1>
</div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-13203766414292977742014-09-30T01:56:00.000-07:002014-09-30T01:56:10.364-07:00How Can Agile Scrum Reduce Regression During Software Development?<div dir="ltr" style="text-align: left;" trbidi="on">
For IT development companies, and organisations developing computer and digital-devices (smartphones, tablets, digital diaries, etc.) software projects, one of the most important, and also the most troublesome issue is encountering “bugs” or defects in the code functionality when a particular application, or a system, is deployed and used in a live environment. Software bugs can be very common. Ever since computers were designed in the yearly years, bugs have inadvertently, or otherwise, kept on troubling coders and project managers, and have tested their ingenuity to resolve them to the fullest extent possible. Ask any seasoned programmer - He or she will tend to initially confer, and eventually say that the word “Bug” is aptly named – It tends to “bug” you!<br />
<br />
<b>Etymology of the word “Bug”</b><br />
It is interesting to know how the terminology “bug” was first coined, and used to describe a state of functioning in which an error, or a flaw in coding can lead to flawed results, or “outputs” in IT jargon. There are several stories as to how the terminology came into existence. A theory most subscribed to involves the pioneer programmer, Grace Hopper, who was a young Naval Reserve officer working on a Mark II computer at Harvard University. In 1944, she related an incident in which the computer had malfunctioned – an actual moth had, in fact, “managed” somehow to get itself embedded between two electrical relays, causing the computer to halt in its functioning. She explained that the cause of malfunction was a “bug,” which was later removed by a technician. The famous bug was exhibited by the Navy for many years, and is now owned by the Smithsonian Institute.<br />
<br />
<b>Bugs and software regression</b><br />
In a broad sense, a software bug can be understood as an error, failure, flaw, or even a fault in the code designed to develop an application or a computer based system. Bugs typically create unexpected and incorrect results or outputs, which cause the functionality of the particular application to stop, or function in a manner other than so desired. Bugs generally arise owing to reasons such as:<br />
<br />
Mistakes carried out while encoding a program<br />
Designing improper code structure or logic<br />
Utilising the functionality of the code in a manner other than that recommended<br />
Technical errors in the code compilers and/or interpreting resources and agents<br />
Of course, the above are not the only causes which give rise to bugs, however, they constitute the major reasons why bugs tend to occur in majority of the cases. When the numbers of bugs increase significantly, the overall functionality of the application may be compromised upon to a considerable level, rendering it useless and non-productive. This can cause severe financial loses, and even force businesses to face litigations from troubled end-users and consumers.<br />
<br />
Broadly, the word “regression” means to return to a former, or a lesser developed state. So, how can regression be understood in terms of “software regression” pertaining to software development? In practice, developers write down, or generate code, to develop a particular functionality as requested by the end-user or the client. During the coding stage, the developer not only develops the code, but also checks it and ensures that it is working properly. This is a standard practice followed by most experienced programmers and developers. However, at times, the testing process may not be carried out properly, or the code functionality might work properly in most cases, but fail to work under certain circumstances and situations. A second scenario is the code may be developed and properly tested at the time of creation, and the application deployed in a successful manner. However, a newer version of the deployed functionality may be subsequently re-developed to include even more features and functionality, to replace the prior one. The reason could be a need experienced by end-users to use the functionality for a more specific purpose. The newer version may cause some of the older functionality to stop working. This, in a rough sense, can be understood as software regression.<br />
<br />
For example, you could encode a program to display “Hello World” on the monitor. It might work perfectly, and display the message each and every time it is executed. Later on, the same code may be re-developed to accept the user’s name, and display it in lieu of “World.” The objective of the new code might be to display “Hello John” rather than “Hello World.” However, once the newer code is developed and deployed, it actually ends up displaying the user’s name only - “John” - instead of the actual greeting “Hello John.” In this case, some of the older functionality associated with displaying “Hello” in the greeting is curtailed due to some coding reason and “missed out” by the newer code. This is software regression.<br />
<br />
<b>Knowing a “bit” about what is Agile Scrum framework</b><br />
Agile is a framework. It offers guidelines as to how software based projects can be effectively developed through consistent and sustained delivery of software functionality through short bursts of development activities known as “sprints.” Agile is based upon certain principles which suggest how the framework ought to be ideally understood and interpreted by people, and how the framework should function in an ideal working environment. One of the Agile principles state “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.” To support this principle, Agile framework supports an iterative (repetitive) product incremental cycle (a process through which smaller components or parts of the actual product are individually developed, and later integrated to form the complete product). At the end of one product increment cycle (sprint), Agile events known as the “Sprint Review” and “Sprint Retrospective” are held to ascertain the reliability of the code functionality developed during the sprint, and whether it satisfies the acceptance criteria so it can be considered as “bug free” and fully functional. Agile promotes “shippable” product increments i.e. small pieces of code offering a certain functionality that is complete, perfectly functional, and free of any “manufacturing” defects.<br />
<br />
It is worth knowing about the actual Agile process, events, roles, and artefacts which can help to eliminate bugs, and control the factors causing regression in software code. People new to Agile concepts and principles may find the framework difficult to understand. This article does not aim to educate the reader in Agile or Scrum framework. Rather, it aims to explain some of the important Agile characteristics which make the framework a very good choice for developing software projects. The objective is to describe how Agile can help to reduce regression levels during the development process. To understand how Agile can do this, it is important to know a “bit” about Agile first.<br />
<br />
<b>The product owner “PO” (Role)</b><br />
He or she is the person who “owns” the project on behalf of the stakeholders or project owners. The person represents the interests of the stakeholders in the Agile project, and ensures that the project delivers a certain business value (importance in terms of market value and financial implications) at all times while the product is being developed. The individual is primarily responsible for the success or failure of the project.<br />
<br />
<b>The product backlog (Artefact)</b><br />
It is a master list mentioning all features and functionalities to be developed in the software project, and to manufacture the software product in totality.<br />
<br />
<b>Product backlog item “PBI” or user story (Artefact)</b><br />
In Agile scrum, the actual product is “broken down” into much smaller, manageable, and developable parts known as product backlog items “PBIs,” or user stories. Each developable sub-unit or product item exists independently in the backlog. Moreover, each PBI is defined to include:<br />
<br />
An index or a reference number to uniquely identify the PBI<br />
A description stating the functionality to be developed<br />
An explanation describing what the functionality is supposed to deliver, how it is to be delivered, and why it is needed<br />
A list of acceptance criteria which needs to be satisfied for the PBI to be considered as “perfect” and “complete”<br />
A short explanation describing what must be “done” for the PBI to be considered as “shippable” and ready for immediate use<br />
<br />
<b>Sprint planning meeting (Event)</b><br />
The iterative product development cycle (sprint) is initiated by an Agile event known as “sprint planning.” This meeting is important from the development point of view. The meeting is held in two parts. In the first half, the PO selects important PBIs or user stories for development purposes from the product backlog, and a temporary list known as a “sprint backlog” is prepared to hold the user stories for development purpose. The PO then explains to the development team how the stories should be developed, and what activities team members should carry out to make the development “acceptable.” The acceptance criteria is properly explained to the team, so each developer becomes familiar as to how the actual development activity should be carried out, and what the management expects out of the proposed development.<br />
<br />
In the second half of the meeting, the development team discusses how user stories should be distributed amongst the developers in the team. Stories are generally distributed based on the expertise and skill sets possessed by the developers. Individuals are assigned development tasks based upon their familiarity with the development process and their experience levels.<br />
<br />
<b>Sprint backlog (Artefact)</b><br />
It is a temporary list created by the PO during the sprint planning meeting to hold the PBIs, or user stories, for development purpose. In Agile, development is always carried out in short bursts of activity known as sprints, and at any given time, a small subset of the product is actually developed. Unlike the traditional waterfall method, development is never carried out in “whole.” The entire sprint backlog is processed for development during the sprint.<br />
<br />
<b>Daily sprints (Event)</b><br />
The “heart” of all Agile frameworks, daily sprints form the base of all development activities. Sprints generally last for two weeks, but can extend up to a maximum of one month. Agile sprints are fundamentally product increment cycles which keep on repeating until the entire product is developed in bits and pieces.<br />
<br />
<b>The sprint review (Event)</b><br />
It is an Agile event held immediately after a particular sprint, or a product increment cycle is completed, and a certain code functionality in the form of user story is developed by the team. The meeting is headed by the Product Owner who verifies the development, and ensures that the user story satisfies the definition of “Done” as mentioned in the PBI. If the user story fails to satisfy the acceptance criteria so stated, it is sent back to the product backlog for re-development. If it is accepted by the PO, the user story is presented to the stakeholders in the succeeding sprint review event for their acceptance and opinions.<br />
<br />
<b>Sprint retrospective (Event)</b><br />
Held immediately after the sprint review event, the stakeholders preview the user stories developed by the team. The stakeholders offer their opinions regarding how much of business value the user stories actually offer after their development, and whether the stories can be, in fact, considered as “shippable.” The main purpose of the retrospective is to reflect upon what mistakes occurred in the Agile project in the past, and what needs to be learnt from prior mistakes. The retrospective offers an opportunity for the Agile team to communicate with the end-users and project owners, and to get “first hand” information as well as knowledge as to what the stakeholders actually need in their project, and how they had actually envisioned their project at the time of its inception.<br />
<br />
<b>How can Agile Scrum framework help to reduce or eliminate bugs and software regression?</b><br />
Software regression is identified if it exists in the code functionality, checked, rectified, and re-tested during the Agile development process. This is how it happens.<br />
<br />
<b>Starting with the software development process using Agile</b><br />
In Agile, the actual development starts with the creation of the product backlog. Based upon how the stakeholders and project owners have envisioned the software project, and what they desire in terms of product functionality, the PO initially “breaks down” the entire project into PBIs or user stories, which are small, individually developable functional units. Once the master list or the product backlog is created, the PO assigns a business value to each PBI, so that important user stories having a higher “market value” can be developed first. The PO than proceeds to conduct a sprint planning meeting which is attended by all. In the sprint planning meeting, the PO selects some of the important PBIs from the top of the product backlog, and transfers those stories to the sprint backlog so the development team can start with its coding activity. It is important to know that developers and programmers only develop those user stories which have been transferred to the sprint backlog, and none of the other PBIs stated in the product backlog. The developers then break down the PBIs into individually developable even smaller tasks and distribute them amongst themselves. Each programmer or developer prepares a smaller list which includes all tasks to be developed by him or her during the sprint.<br />
<br />
<b>Carrying out the actual software development</b><br />
The actual product development is carried out through sprints. During the sprint, each developer takes up tasks allotted to him or her, and proceeds with their development. At a time, one task is taken up for development. Once the task is completed, it is marked as “Completed” and another task is subsequently taken up for development. The process is repeated until all the tasks are developed. Once a particular task is completed, it is tested for its reliability, consistency, and accuracy by team members specially appointed to carry out the testing process. Some Agile processes maintain a separate team for carrying out the Q.A. related activities. Each task is painstakingly checked for any errors arising through improper coding practices, wrong usage of coding language, flawed design, and other regression related parameters. Agile teams can also use specially developed regression testing software to identify any flaws in the coding, designing, or functionality aspects. Once the regression checking is over, the user story is verified whether it fulfils the benchmark and acceptance criteria mentioned in the PBI. After the story is thoroughly checked, it is marked as “Completed” and its status updated in the Agile process flow. It is important to complete all the tasks allotted to the team members during the sprint.<br />
<br />
<b>After the development activity</b><br />
After all user stories have been developed by the development team during the sprint, an Agile event known as the sprint review is held to present the development carried out to the PO. During the sprint review, the PO scrutinises each user story and re-verifies whether they fulfil the acceptance criteria, and whether they, in fact, meet the definition of “Done.” If any user story fails to satisfy the PO, it is transferred back to the product backlog from where it may be taken up for re-development at a later stage. Only bug free, well documented, and “shippable” user stories should be accepted as “final” during the sprint review. The objective of the event is to check for any regression related issues at a “micro” level.<br />
<br />
Once the sprint review event is over, another Agile event known as the sprint retrospective is held to further ascertain whether the user story functionality is acceptable from the market point of view. The stakeholders, project owners, end users, and other technically oriented staff members attend this event. The user story functionality is demonstrated to the participants, who minutely scrutinise the functionality aspects and working to find any flaws or incorrect functioning of the user story. The participants also determine how much worth the functionality is from the saleability and market point of view. Once the stakeholders are satisfied with the results, the user story is accepted as “Done.” The aim of this event is to check for regression related issues at a “macro” level.<br />
<br />
<b>Agile Scrum and software regression</b><br />
Each task, when completed by the team during the daily sprint, can be individually tested for bugs, design flaw, and regression. In Agile, the user story cannot be accepted until it fulfils the acceptance criteria and meets the benchmarks. At the time of development, the developer initially checks the user story for any bugs, or errors of any kind. Once the development team Okays the functionality, it is checked and verified again by the PO. POs are usually experienced Agile professionals, and have the knowledge, as well as the ability to find any bugs or flaws overlooked by the team. This is how bugs are eliminated at a micro level. Once the PO acknowledges the user story, it is exhibited to the stakeholders who are familiar with the market trends and conditions, and know what kind of functionality a particular user story should offer to satisfy the end user’s requirements. They again check the functionality from the end user’s point of view, and if it does not proffer to fulfil what the end users need, they reject the user story. When any user story reaches the sprint retrospective stage, it will not possess any bugs or coding errors, which are detected in the preceding micro level stages. The development is checked at a macro level during the retrospective, and accepted by the end users.<br />
Source:- <b><a href="http://www.quickscrum.com/Kernel/Article/frmArticleDetails.aspx?PAGE_TITLE=How%20Can%20Agile%20Scrum%20Reduce%20Regression%20During%20Software%20Development%3F&ARTICLE_ID=22" target="_blank">How Can Agile Scrum Reduce Regression During Software Development?</a></b><br />
<br /></div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com1tag:blogger.com,1999:blog-651611792114842420.post-85207948624947683212014-09-16T06:43:00.003-07:002014-09-16T06:47:54.902-07:00Scrum Tool<div dir="ltr" style="text-align: left;" trbidi="on">
<br />
<table id="tblArticle" style="background-color: white; color: #555555; font-family: Arial, Helvetica, sans-serif; font-size: 13px; padding-top: 20px; width: 100%px;"><tbody>
<tr id="trTraining_3"><td align="left" class="wordwrap" id="tdArticleDetail_19" style="display: inline-block; width: 940.5px; word-wrap: break-word;"><div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">QuickScrum helps to unlock the power of Agile Scrum into your projects – whether you are </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">a “seasoned” Agile professional or a novice - just starting with Scrum – you can get started with </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Scrum implementation and get your projects “going” right away!</span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">The <strong><a dir="ltr" href="http://www.quickscrum.com/" target="_blank">Scrum tool</a></strong> plays an indispensable part in planning and developing your software projects.</span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">It can help you:</span></div>
<ul>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Create and estimate user stories</span></span></li>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Effortlessly create and <strong><a dir="ltr" href="http://www.quickscrum.com/Kernel/frmFeature.aspx" target="_blank">maintain product backlogs</a></strong></span></span></li>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Define and design your sprints</span></span></li>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Identify team progress and velocity through dynamically generated burndown and </span></span></li>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">velocity charts</span></span></li>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Visualise the entire team activity on a “single” platform</span></span></li>
<li style="text-align: justify;"><span style="font-size: 14px;"><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Avail customised reports to get an insight about your project’s status.</span></span></li>
</ul>
<h2 style="color: #333333; font-size: 24px; font-weight: normal;">
<span style="font-size: 18px;"><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">QuickScrum <a dir="ltr" href="http://www.quickscrum.com/" target="_blank">Scrum tool</a> advantages</span></span></h2>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">The tool offers many benefits and is a “must have” for all Scrum whiteboard users. The tool </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">offers several facilities and features that are not found, and not possible to have while </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">using a traditional whiteboard. It offers an “automated” Scrum implementation solution for the </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">entire team.</span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"><br /></span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"><strong>Search anything at your fingertips</strong><br style="margin: 0px;" />A trademark feature of the tool, very few other Scrum tools offer a facility wherein you can </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">search for any type of project related information without leaving your current page. Envisioned </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">and designed specially to aid the Scrum team, the search features ensure you have quick and </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">easy access to any aspect or information pertaining to your ongoing project. Find, check, edit, </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">and delete whatever you need to – instantly! </span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"><br /></span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"><strong>Manage product backlogs of any size and complexity</strong><br style="margin: 0px;" />Product backlogs form the “heart” of a Scrum based software project. The tool supports creation </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">of new user stories, their modification, and removal. It is very easy to create, search, and list </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">out user stories based upon your specific searching criteria. The product backlog </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">management supports drag-and-drop features which help in the backlog grooming activity. </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">It is easy to carry out the backlog refinement sessions with the entire team using the </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">backlog management features. What’s more, you can create and maintain product backlogs </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">of any size and complexity. </span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"><br /></span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"><strong>Plan multiple sprints simultaneously</strong><br style="margin: 0px;" />Multiple sprints can be designed and planned on a single page.</span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"><br /></span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"><strong>Access Scrum taskboard from anywhere</strong></span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Very essential for distributed or disjoint development teams, the tool offers a common, shared </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">access to all team members. Each member can log on and view instant updates on the taskboard.</span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"> The taskboard helps to foster collaboration through live updates of activity carried out by other </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">team members. The taskboard features can be accessed from anywhere.</span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"><br /></span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"><strong>Live Burndown charts</strong><br style="margin: 0px;" />Generate burndown charts that display the most current team progress. Compare ideal team </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">progress with your current team velocity and monitor projects in a dynamic way. An essential tool </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">for product owners and scrum masters to keep track of current team activity and progress.</span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"><br /></span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"><strong>Instant team activity log</strong><br style="margin: 0px;" />Whatever activity you do – whether the tool users create a new user story, add, or update tasks </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">– everything is “logged” and displayed “live” in the activity log section of the tool. See what </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">other team members are currently up to and “doing” in the tool.</span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"><br /></span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"><strong>Detailed velocity charts</strong><br style="margin: 0px;" />Informative and visually appealing velocity charts exhibit the current team velocity.</span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"><br /></span></div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"><strong>Resources workload and summary</strong><br style="margin: 0px;" />The QuickSCrum tool displays tasks linked to individual resources and their task statuses, in </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">terms of time available, associated with each team member. The resource workload summary</span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"> is exhibited, so it can be identified how much additional work can be taken up and completed </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">by the programmers.Read more at <b><a href="http://www.quickscrum.com/Kernel/Tools/scrum-tools.aspx" target="_blank">Scrum tool</a></b></span></div>
</td></tr>
</tbody></table>
</div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-29961008017536880122014-08-22T03:17:00.004-07:002014-08-22T03:17:48.189-07:00Main Differences Between Agile Scrum And XP Framework<div dir="ltr" style="text-align: left;" trbidi="on">
<div style="background-color: white; border: 0px; color: #333333; font-family: Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 1em; margin-top: 1em; outline: 0px; padding: 0px; vertical-align: baseline;">
Of all <strong style="border: 0px; font-family: inherit; font-style: inherit; font-variant: inherit; line-height: inherit; margin: 0px; outline: 0px; padding: 0px; vertical-align: baseline;"><a href="http://www.quickscrum.com/" rel="nofollow" style="border: 0px; color: #7b539d; font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; line-height: inherit; margin: 0px; outline: 0px; padding: 0px; text-decoration: none; vertical-align: baseline;" target="_blank">Agile frameworks</a></strong>, scrum is the most popular one. Scrum methodology is highly<br />recommended for developing IT projects and it is so widely recommended for it that it is often<br />confused with Extreme Programming or “XP” Agile framework, which is synonymous with<br />software development. Both the frameworks are much similar, and to a person not<br />conversant with Agile, both might appear to be the same at a first glance. While most<br />Agile processes and events remain the same, there are some subtle differences between<br />the two frameworks.</div>
<div style="background-color: white; border: 0px; color: #333333; font-family: Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 1em; margin-top: 1em; outline: 0px; padding: 0px; vertical-align: baseline;">
<strong style="border: 0px; font-family: inherit; font-style: inherit; font-variant: inherit; line-height: inherit; margin: 0px; outline: 0px; padding: 0px; vertical-align: baseline;">Sprint durations</strong><br />Typically, in scrum, the sprint iteration can last from two weeks up to one month. In XP,<br />the duration is much shorter, and generally lasts from one to two weeks. The sprint<br />duration does not exceed two weeks in XP.</div>
<div style="background-color: white; border: 0px; color: #333333; font-family: Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 1em; margin-top: 1em; outline: 0px; padding: 0px; vertical-align: baseline;">
<strong style="border: 0px; font-family: inherit; font-style: inherit; font-variant: inherit; line-height: inherit; margin: 0px; outline: 0px; padding: 0px; vertical-align: baseline;">Committing the sprint backlog</strong><br />One of the major differences, and an important one too, is how user stories are<br />committed in the sprint backlog while implementing scrum and XP. In scrum, the sprint<br />backlog is “owned” by the development team. Once the team accepts the sprint backlog,<br />all the <strong style="border: 0px; font-family: inherit; font-style: inherit; font-variant: inherit; line-height: inherit; margin: 0px; outline: 0px; padding: 0px; vertical-align: baseline;"><a href="http://www.quickscrum.com/Kernel/frmFeature.aspx" rel="nofollow" style="border: 0px; color: #7b539d; font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; line-height: inherit; margin: 0px; outline: 0px; padding: 0px; text-decoration: none; vertical-align: baseline;" target="_blank">user stories</a></strong> in the backlog are “committed” for development purposes. The team<br />is required to complete all the user stories stated in the backlog. Moreover, once<br />committed, the sprint backlog cannot be “changed” while implementing scrum. If any<br />new user story is required to be developed, it can only be included in the next sprint after<br />a new sprint planning meeting is conducted. This is not the case with XP. The sprint<br />backlog does not become “static” even after it is accepted by the team and the user<br />stories are taken up for development. If required, based upon the feedback received<br />from the stakeholders, a user story taken up for development can be replaced with a<br />nother one having the same estimation in terms of story points. Therefore, the sprint<br />backlog is not “committed” at any time in XP. New stories can be replaced in lieu of<br />those currently existing in the backlog – something that is impossible in scrum. However,<br />it is important to know that such a “replacement” of user story is only possible in XP<br />before the particular user story is taken up for execution in the daily sprint. Once the<br />development of a user story starts in XP, it cannot be replaced. Read more at <a href="http://goo.gl/35Yq67" rel="nofollow" style="border: 0px; color: #7b539d; font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; line-height: inherit; margin: 0px; outline: 0px; padding: 0px; text-decoration: none; vertical-align: baseline;" target="_blank">http://goo.gl/35Yq67</a></div>
<div class="center" style="background-color: white; border: 0px; color: #333333; font-family: Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 1em; margin-top: 1em; outline: 0px; padding: 0px; text-align: center; vertical-align: baseline;">
<strong style="border: 0px; font-family: inherit; font-style: inherit; font-variant: inherit; line-height: inherit; margin: 0px; outline: 0px; padding: 0px; vertical-align: baseline;"><a href="http://www.quickscrum.com/Kernel/frmPricing.aspx" rel="nofollow" style="border: 0px; color: #7b539d; font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; line-height: inherit; margin: 0px; outline: 0px; padding: 0px; text-decoration: none; vertical-align: baseline;" target="_blank">Subscribe Free scrum tool from Quickscrum.com</a></strong></div>
</div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-67812614717292959132014-08-12T06:29:00.000-07:002014-08-12T06:52:36.097-07:00How Can Agile Scrum Reduce Regression During Software Development?<div dir="ltr" style="text-align: left;" trbidi="on">
<table id="tblArticle" style="color: #555555; font-family: Arial, Helvetica, sans-serif; font-size: 13px; padding-top: 20px;"><tbody>
<tr id="trTraining_3"><td class="wordwrap" id="tdArticleDetail_22" style="display: inline-block; width: 940.5px; word-wrap: break-word;"><div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">For IT development companies, and organisations developing computer and digital-devices </span></div>
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">(smartphones, tablets, digital diaries, etc.) software projects, one of the</span></div>
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"> most important, and also the most troublesome issue is encountering “bugs” or defects in</span></div>
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"> the code functionality when a particular application, or a system, is deployed and used in </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">a live </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">environment. Software bugs can be very common. Ever since computers were </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">designed in </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">the yearly years, bugs have inadvertently, or otherwise, kept on troubling </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">coders and project </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">managers, and have tested their ingenuity to resolve them to the </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">fullest extent possible. </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Ask any seasoned programmer - He or she will tend to initially </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">confer, and eventually say that the word</span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;"> “Bug” is aptly named – It tends to “bug” you!</span></div>
</div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<br />
<div style="text-align: left;">
<strong style="font-family: 'trebuchet ms', helvetica, sans-serif;"><big>Etymology of the word “Bug”</big></strong></div>
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"></span><br />
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">It is interesting to know how the terminology “bug” was first coined, and used to </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">describe a state </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">of functioning in which an error, or a flaw in coding can lead to </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">flawed results, or “outputs” in IT </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">jargon. There are several stories as to how the </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">terminology came into existence. A theory most </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">subscribed to involves the pioneer</span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"> programmer, Grace Hopper, who was a young Naval Reserve </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">officer working on a </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Mark II computer at Harvard University. In 1944, she related an incident in </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">which </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">the computer had malfunctioned – an actual moth had, in fact, “managed” somehow </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">to get </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">itself embedded between two electrical relays, causing the computer to halt</span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"> in its functioning. She </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">explained that the cause of malfunction was a “bug,” which </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">was later removed by a technician. </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">The famous bug was exhibited by the Navy for</span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"> many years, and is now owned by the Smithsonian </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Institute. </span></div>
</div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<br />
<div style="text-align: left;">
<strong style="font-family: 'trebuchet ms', helvetica, sans-serif;"><big>Bugs and software regression</big></strong></div>
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"></span><br />
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">In a broad sense, a software bug can be understood as an error, failure, flaw, or </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">even a fault in the </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">code designed to develop an application or a computer based </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">system. Bugs typically create unexpected </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">and incorrect results or outputs, which </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">cause the functionality of the particular application to stop, </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">or function in a manner </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">other than so desired. Bugs generally arise owing to reasons such as:</span></div>
</div>
<ul>
<li style="text-align: left;"><span style="font-size: 14px;"><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Mistakes carried out while encoding a program</span></span></li>
<li style="text-align: left;"><span style="font-size: 14px;"><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Designing improper code structure or logic</span></span></li>
<li style="text-align: left;"><span style="font-size: 14px;"><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Utilising the functionality of the code in a manner other than that recommended</span></span></li>
<li style="text-align: left;"><span style="font-size: 14px;"><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Technical errors in the code compilers and/or interpreting resources and agents</span></span></li>
</ul>
<div style="text-align: justify;">
<div style="text-align: left;">
<span style="color: #4b4c4d; font-family: trebuchet ms, helvetica, sans-serif;"><span style="font-size: 14px;">Of course, the above are not the only causes which give rise to bugs, however, they </span></span><br />
<span style="color: #4b4c4d; font-family: trebuchet ms, helvetica, sans-serif;"><span style="font-size: 14px;">constitute the </span></span><span style="color: #4b4c4d; font-family: 'trebuchet ms', helvetica, sans-serif; font-size: 14px;">major reasons why bugs tend to occur in majority of the cases. When</span><br />
<span style="color: #4b4c4d; font-family: 'trebuchet ms', helvetica, sans-serif; font-size: 14px;"> the numbers of bugs increase </span><span style="color: #4b4c4d; font-family: 'trebuchet ms', helvetica, sans-serif; font-size: 14px;">significantly, the overall functionality of the application</span><br />
<span style="color: #4b4c4d; font-family: 'trebuchet ms', helvetica, sans-serif; font-size: 14px;"> may be compromised upon to a considerable </span><span style="color: #4b4c4d; font-family: 'trebuchet ms', helvetica, sans-serif; font-size: 14px;">level, rendering it useless and </span><br />
<span style="color: #4b4c4d; font-family: 'trebuchet ms', helvetica, sans-serif; font-size: 14px;">non-productive. This can cause severe financial loses, and </span><span style="color: #4b4c4d; font-family: 'trebuchet ms', helvetica, sans-serif; font-size: 14px;">even force businesses </span><br />
<span style="color: #4b4c4d; font-family: 'trebuchet ms', helvetica, sans-serif; font-size: 14px;">to face litigation from troubled end-users and consumers.</span></div>
</div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Broadly, the word “regression” means to return to a former, or a lesser developed </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">state. So, </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">how can regression be understood in terms of “software regression”</span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"> pertaining to software </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">development? In practice, developers write down, </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">or generate code, to develop a particular functionality </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">as requested by the </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">end-user or the client. During the coding stage, the developer not only develops </span></div>
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">the code, but also checks it and ensures that it is working properly. This is a </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">standard practice followed </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">by most experienced programmers and developers.</span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"> However, at times, the testing process may not </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">be carried out properly, or the </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">code functionality might work properly in most cases, but fail </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">to work under </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">certain circumstances and situations. A second scenario is the code may be </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">developed </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">and properly tested at the time of creation, and the application </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">deployed in a successful manner. </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">However, a newer version of the deployed </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">functionality may be subsequently re-developed to </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">include even more features </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">and functionality, to replace the prior one. The reason could be a need </span></div>
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">experienced by end-users to use the functionality for a more specific purpose. </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">The newer version </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">may cause some of the older functionality to stop working.</span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"> This, in a rough sense, can be understood </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">as software regression.</span></div>
</div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">For example, you could encode a program to display “Hello World” on the monitor.</span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"> It might work </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">perfectly, and display the message each and every time it is executed.</span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"> Later on, the same code </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">may be re-developed to accept the user’s name, and display</span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"> it in lieu of “World.” The objective of the</span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">new code might be to display </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">“Hello John” rather than “Hello World.” However, once the newer </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">code is developed </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">and deployed, it actually ends up displaying the user’s name only - “John” - instead </span></div>
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">of the actual greeting “Hello John.” In this case, some of the older functionality associated </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">with </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">displaying “Hello” in the greeting is curtailed due to some coding reason and </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">“missed out” by </span></div>
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">the newer code. This is software regression. </span></div>
</div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<br />
<div style="text-align: left;">
<strong style="font-family: 'trebuchet ms', helvetica, sans-serif;"><big>Knowing a “bit” about <a href="http://www.quickscrum.com/Kernel/frmQSImplementation.aspx">what is Agile Scrum framework</a></big></strong></div>
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"></span><br />
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Agile is a framework. It offers guidelines as to how software based projects can be </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">effectively developed </span></div>
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"></span><br />
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">through consistent and sustained delivery of software functionality through short bursts </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">of development </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">activities known as “</span><strong style="font-family: 'trebuchet ms', helvetica, sans-serif;"><a dir="ltr" href="http://www.quickscrum.com/" target="_blank"><span style="color: green;">sprints</span></a></strong><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">.” Agile is based upon certain principles which </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">suggest how the </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">framework ought to be ideally understood and interpreted by people, </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">and how the framework </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">should function in an ideal working environment. One of the </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Agile principles state “Our highest </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">priority is to satisfy the customer through early </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">and continuous delivery of valuable software.” To </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">support this principle, Agile </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">framework supports an iterative (repetitive) product incremental cycle </span></div>
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">(a process through which smaller components or parts of the actual product are individually </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">developed,</span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">and later integrated to form the complete product). At the end of one product </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">increment cycle (sprint)</span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">,</span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">Agile events known as the “Sprint Review” and “Sprint Retrospective” </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">are held to ascertain the </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">reliability of the code functionality developed during the sprint, </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">and whether it satisfies the </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">acceptance </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">criteria so it can be considered as “bug free” </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">and fully functional. Agile promotes “shippable” </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">product increments i.e. small pieces of </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">code offering a certain functionality that is complete, </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">perfectly functional, and free </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">of any “manufacturing” defects.</span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">It is worth knowing about the actual Agile process, events, </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">roles, and artefacts which can help to </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">eliminate bugs, and control the factors causing </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">regression in software code. </span><em style="font-family: 'trebuchet ms', helvetica, sans-serif;">People new to Agile </em><em style="font-family: 'trebuchet ms', helvetica, sans-serif;">concepts and principles may find the </em><br />
<em style="font-family: 'trebuchet ms', helvetica, sans-serif;">framework difficult to understand. This article does not aim to </em><em style="font-family: 'trebuchet ms', helvetica, sans-serif;">educate the reader in </em><br />
<em style="font-family: 'trebuchet ms', helvetica, sans-serif;">Agile or Scrum framework. Rather, it aims to explain some of the important </em><em style="font-family: 'trebuchet ms', helvetica, sans-serif;">Agile </em><br />
<em style="font-family: 'trebuchet ms', helvetica, sans-serif;">characteristics which make the framework a very good choice for developing software </em><br />
<em style="font-family: 'trebuchet ms', helvetica, sans-serif;">projects. </em><em style="font-family: 'trebuchet ms', helvetica, sans-serif;">The objective is to describe how Agile can help to reduce regression levels during </em><br />
<em style="font-family: 'trebuchet ms', helvetica, sans-serif;">the development </em><em style="font-family: 'trebuchet ms', helvetica, sans-serif;">process. To understand how Agile can do this, it is important to know a </em><br />
<em style="font-family: 'trebuchet ms', helvetica, sans-serif;">“bit” about Agile first.</em></div>
</div>
<div style="color: #4b4c4d; font-size: 14px; text-align: justify;">
<br />
<div style="text-align: left;">
<strong style="font-family: 'trebuchet ms', helvetica, sans-serif;"><big>The <a href="http://www.quickscrum.com/">product owner</a> “PO” (Role)</big></strong></div>
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"></span><br />
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">He or she is the person who “owns” the project on behalf of the stakeholders or project </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">owners. </span></div>
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;"></span><br />
<div style="text-align: left;">
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">The person represents the interests of the stakeholders in the Agile project, and ensures </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">that the </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">project delivers a certain business value (importance in terms of market value </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">and financial implications) </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">at all times while the product is being developed. The individual </span><br />
<span style="font-family: 'trebuchet ms', helvetica, sans-serif;">is primarily responsible for the </span><span style="font-family: 'trebuchet ms', helvetica, sans-serif;">success or failure of the project.</span></div>
</div>
<div style="text-align: justify;">
<div style="text-align: left;">
<strong style="color: #4b4c4d; font-family: 'trebuchet ms', helvetica, sans-serif; font-size: 14px;"><big><a href="http://www.quickscrum.com/Kernel/frmFeature.aspx">The product backlog</a> (Artefact)</big></strong></div>
<div style="text-align: left;">
<span style="color: #4b4c4d; font-family: trebuchet ms, helvetica, sans-serif;"><span style="font-size: 14px;">It is a master list mentioning all features and functionalists to be developed in the </span></span><br />
<span style="color: #4b4c4d; font-family: trebuchet ms, helvetica, sans-serif;"><span style="font-size: 14px;">software project,</span></span><span style="color: #4b4c4d; font-family: 'trebuchet ms', helvetica, sans-serif; font-size: 14px;">and to manufacture the software product in totality. Read more at</span></div>
<u><b><a href="http://goo.gl/Gy8PXu">http://goo.gl/Gy8PXu</a></b></u></div>
</td></tr>
</tbody></table>
</div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-88090154577252745902014-08-06T23:19:00.001-07:002014-08-06T23:19:09.119-07:00QuickScrum Tool<iframe allowfullscreen="" frameborder="0" height="344" src="//www.youtube.com/embed/Zc8dcMSmvjc" width="459"></iframe>Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-76276300723741665312014-07-24T06:20:00.000-07:002014-07-24T06:20:11.291-07:00<a href="http://www.bloglovin.com/blog/12617551/?claim=k72ee4yfeun">Follow my blog with Bloglovin</a>Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-50208816837016336372014-07-24T00:14:00.000-07:002014-07-24T00:19:41.905-07:00Is Agile Scrum suitable For Software Development?<div dir="ltr" style="text-align: left;" trbidi="on">
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<b>The scope of
development in the software/IT field<o:p></o:p></b></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
People and individuals associated with software development and the
IT field like to use the term “software development” to describe their
particular field of work and professional involvement. The term “development”
is very widely used to describe a host of activities catering to the IT field.
It can range from developing code for applications and systems, to developing
mobile applications for mobile operating systems such as Android, iOS, Symbian,
Windows OS, etc. (visit http://en.wikipedia.org/wiki/Mobile_operating_system), “manufacturing”
gaming software using scripting languages like Ruby, AGSScript, Lua, Marathon
markup language, Ada, C++, C#, D, Lisp, Mercury, Pascal, Perl, Python, Scheme,
JavaScript, Java, VBscript, EDL, etc., (visit http://en.wikipedia.org/wiki/List_of_programming_languages) carrying out web
development using HTML, CSS, PHP, Joomla, DotNetNuke, Java, etc., and even
developing entire operating systems for tablets and PCs (visit http://en.wikipedia.org/wiki/List_of_operating_systems, to know more about
operating systems). The fact is as on today, the terminology “software
development” is extensively used to mention almost any type or activity
associated with the programming and development of “computerizable” code of any
type, in any way, or manner. When a particular methodology or framework is used
to develop computerizable code and create software projects, it is important to
ascertain whether the scope of development includes the specific activity you’re
currently involved or associated with. Software development and <b><a href="http://www.quickscrum.com/Kernel/frmSupport.aspx">projectmanagement frameworks such as Agile</a></b> have the potential to develop successful IT
related projects involving the vast majority of development platforms and
operating systems. <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<b><a href="http://www.quickscrum.com/Kernel/frmPartner.aspx">What is Agileframework?</a><o:p></o:p></b></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
While explaining Agile in a simple and straightforward manner, it
can be best understood as a collection of project development methodologies and
frameworks, of which any framework or methodology can be used in a successful
manner to dynamically develop projects of almost any type and nature, including
software development projects. The framework is based upon iterative and
incremental development, in which self-organised and self-managing development
teams understand, plan, and develop projects under the supervision of a project
leader, and offer productivity in the form of short bursts of development
cycles (iterative development) known as sprints. A unique feature of all Agile
frameworks is that the development carried out by the team is “shippable” in
nature i.e. the code developed during the product development cycle is
independent, testable, verifiable,
documentable, and ready for deployment after it is stringently checked
for any “manufacturing” defects. <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
A second, highly important feature of Agile development is that
individuals “owning” the project are closely linked with the approval of
development carried out by the team. A particular “code” or “piece” of functionality
is checked for regression after it is developed, and subsequently presented to
the stakeholders and project owners. They ascertain the development carried
out, and clear it as “OK” for future integration into the actual product. This
leads to a successful development of software projects, since the management is
always aware about what functionality is currently being developed by the team,
and up to what extent it satisfies the project objectives. If the project
owners feel the productivity offered by the team is not up-to-the-mark, or
fails to satisfies them in terms of business value (how much important the code
or functionality is from the market point of view, and how much it is worth
from the financial point of view) offered by the functionality, they can reject
the entire functionality and instruct the project manager to redevelop the
particular script or code, based upon a new set of inputs and requirements recommended
by them. This ensures that the software project always “maintains” its business
value at all times, even while the product is being currently developed. <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
A third important feature of Agile framework is that all activities
in the project are “time boxed”, and therefore, have to be completed within a
predetermined time period. In an Agile project, each activity is time bound.
All development related activities are “configured” to suit the unique project
needs, and a duration “affixed” to them so they can be completed within a
stipulated time. This ensures that the project does not “drag-on” and extend
indefinitely. The development costs incurred while the project is being
developed can be properly and “profitably” controlled, so that the project does
not become “too” expensive and difficult to afford financially.<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<b><a href="http://www.quickscrum.com/Kernel/frmFeature.aspx">Agile principles and features</a><o:p></o:p></b></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
Agile framework differs drastically when compared to traditional
linear or Waterfall methodology. In Agile, project development is carried out
in short bursts of activities rather than in stages that have to be “completed”
one after the other. <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
The main Agile features include:<o:p></o:p></div>
<div class="MsoListParagraphCxSpFirst" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify; text-indent: -14.2pt;">
<!--[if !supportLists]--><span style="font-family: Symbol;">·<span style="font-family: 'Times New Roman';"> </span></span><!--[endif]-->Cross-functional
development teams consisting of developers, programmers, testers, QA personnel,
technical writers, system analysts, etc. all work together as a single
composite team through collaborative efforts, offer and share ideas, and help
each other during the development process.<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify; text-indent: -14.2pt;">
<!--[if !supportLists]--><span style="font-family: Symbol;">·<span style="font-family: 'Times New Roman';"> </span></span><!--[endif]-->Working in short,
fast-paced development cycles, with focused objectives – Iterative development.<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify; text-indent: -14.2pt;">
<!--[if !supportLists]--><span style="font-family: Symbol;">·<span style="font-family: 'Times New Roman';"> </span></span><!--[endif]-->Shippable productivity
at the end of iterative development cycles – Incremental development. The
functionality keeps on “growing” through development cycles until the entire
application, system, or product is developed.<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify; text-indent: -14.2pt;">
<!--[if !supportLists]--><span style="font-family: Symbol;">·<span style="font-family: 'Times New Roman';"> </span></span>Human communications
and involvement takes precedence over management authority and delegation of
work.<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify; text-indent: -14.2pt;">
<!--[if !supportLists]--><span style="font-family: Symbol;">·<span style="font-family: 'Times New Roman';"> </span></span>Total transparency and
visibility of the team progress to project owners, stakeholders, and end users.<o:p></o:p></div>
<div class="MsoListParagraphCxSpLast" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify; text-indent: -14.2pt;">
<!--[if !supportLists]--><span style="font-family: Symbol;">·<span style="font-family: 'Times New Roman';"> </span></span>Feedback and
suggestions help to self-correct and offer new ways and means to carry out
quicker, more efficient, and reliable development.<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<i>An important feature of
all Agile frameworks is that the frameworks are independent of the nature of
project to be developed i.e. the framework is not dependent upon the platform
or environment used to develop the particular software project. The architecture
or design can vary, and could be anything. The important aspect is that an Agile
framework has to be implemented in the project first, and its benefits availed
subsequently. Please visit </i><i>http://en.wikipedia.org/wiki/Agile_software_development</i><i>.<o:p></o:p></i></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<b><a href="http://www.quickscrum.com/">What is Agile scrum?</a><o:p></o:p></b></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
Scrum, briefly, is a
“light weight” Agile framework, used extensively for developing and delivering
“workable” software products, very often, and on a consistent basis. The
software products can range from the development of new web processes and
systems, gaming solutions, plugins, mobile apps, ecommerce websites, corporate
portals, development of WordPress themes, RAD (Rapid Application Development)
projects, OOPs (Object Oriented Programming) projects, CAD/CAM drafting
solutions, port programming and configuration utilities, web development and
platform interfacing solutions, etc. Scrum adheres to all Agile principles and
features discussed above since the framework is “inherited” from Agile itself. <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
Scrum offers a new,
and a better way of managing software projects. There are many technical
reasons why Scrum is popular and why many Fortune 500 companies prefer to use
the framework for their project development purposes. While being introduced to
Agile Scrum, a question that inadvertently comes to one’s mind is why is Scrum
so popular? Why is there so much “hype” about Scrum? Does Scrum offer a magic formula,
which can work wonders for your project and software development? Why should an
organisation that has been following a particular development methodology, and
feels comfortable doing so, should change over to Scrum? There is a separate
article which deals entirely with why you should opt for Scrum. The point is,
this article focus upon explaining Scrum to individuals who are new to the
topic, and have absolutely no idea what the framework is all about, and what it
can “do” for you. Efforts have been made to explain that Agile Scrum is
applicable to almost any kind of software development, and possesses certain features
which make the framework very popular as well as “powerful”. <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<b><a href="http://www.quickscrum.com/">How does Scrum work?</a><o:p></o:p></b></div>
<br />
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
The actual Scrum
process can prove to be difficult to understand, at first, for Scrum beginners.
Even though Scrum implementation is not difficult, people need to understand
and familiarize themselves about what is product increment, and how it actually
occurs during the Scrum process. The second aspect is getting to know about
Scrum events. The special meetings, known as “events” are important for
monitoring the development activity, and analysing the reliability and
effectiveness of the functionality developed by the team. They also help to
solicit feedback from the team members as well as the project owners so that
the business value of the project is not affected, and maintained at all times
– even while the product is being developed. It is worthwhile to get an
“overview” of the process first. <span style="font-size: x-small;"><o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="http://www.quickscrum.com/"><img alt="Quickscrum- Scrum tool" border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEimP3kE4TxdtWL9JtVYsLwLJyx2UYgjABFOKy2iXWhcvOmjhOiDgE6BW1pRJ9DARGnBYqTATioNOUQcDpyRA7mwQZ7mwjzml9QO3SUev-0nGtNyHhb9-e529RGabpw5xs5xPzveooRepl_2/s1600/posting-1.png" height="382" style="margin-left: auto; margin-right: auto;" title="Scrum tool" width="400" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;"><a href="http://www.quickscrum.com/"><br /></a></td></tr>
</tbody></table>
<br />
<div class="MsoListParagraphCxSpFirst" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify; text-indent: -14.2pt;">
<!--[if !supportLists]--><b>1.<span style="font-weight: normal;">
</span></b><!--[endif]--><b>Project conception - An idea!<o:p></o:p></b></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
All
projects, whether involving software development, or otherwise, start with an
“idea”. Projects are developed out of needs. A project is planned to fulfil a
particular requirement or achieve a certain objective. Moreover, each project
results into “something” within a specific time frame – a project cannot extend
indefinitely. It is important here to differentiate between a “project” and a
“program”. Programs are generally long termed, and can even last for years,
unlike projects which have a relatively short life span and last for a brief
period, ranging from a couple of months to even a year. <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
Typically,
a person, or a group of individuals realise it is worthwhile to put in efforts
and resources, and develop “something” so that “another thing” can be easily
fulfilled or availed. The “something” is the product, and the “another thing”
is the solution that the project is supposed to provide. This stage of project
development involves a lot of discussion and brain storming sessions, where the
product is envisioned and “though over”. <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
Scrum
does not figure during this stage. However, the vision seen by the project
owners, can, or may, affect the manner in <b><a href="http://www.quickscrum.com/">which Scrum is implemented in theproject</a></b>, in the future. This is because the nature of product to be developed
may require Scrum to be configured in a certain manner to obtain positive
results from the project. <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify; text-indent: -14.2pt;">
<!--[if !supportLists]--><b>2.<span style="font-weight: normal;">
</span></b><!--[endif]--><b>Project release – Getting started with the software
project<o:p></o:p></b></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
Once the
project is “thought about” the next logical step is to work out the
nitty-gritty concerning the project dynamics – the objective of the project,
the product definition, how the project should ideally deliver the product, in
what manner, what should be the “strength” of the team, how many team members,
etc.<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
Scrum development
process does not come into the picture even during this stage. The
documentation pertaining to the project is created and “everything” concerning
the product to be developed is finalised – in black and white. Scrum does not
advocate extensive documentation. You do not have to prepare detailed system
flow diagrams and extensive design structures to get started with Scrum
development. A basic idea will suffice, and you should only spend that much
time and efforts which can get you “started” with the actual development
activity. Just enough information and specifications to develop some of the
most important product features. <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
The
project release is attended by the “Product Owner” – the person who functions
as a project manager in the Scrum project, the Scrum Master who overseas that
Scrum is properly implemented and followed by the team while the project is
being developed, and the stakeholders or project owners who actually sponsor
the project. <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify; text-indent: -14.2pt;">
<!--[if !supportLists]--><b>3.<span style="font-weight: normal;">
</span></b><!--[endif]--><b><a href="http://www.quickscrum.com/Kernel/frmFeature.aspx">Creating the product backlog</a> (Product Features List) –
Defining the product features and functionality<o:p></o:p></b></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
The <a href="http://www.quickscrum.com/Kernel/frmSupport.aspx">Scrum development process</a> starts with the creation of a master list containing all
features and functionality required to create the product in totality. In
simple terms, the entire product, currently existing on paper as “imagined” by
the stakeholders and project owners, is “broken down” into its constituent
parts, consisting of individual features and functionality. The product is
thoughtfully, and systematically, broken down such that each individual
component can be individually developed, tested, and eventually integrated with
other software components or functionality developed by the team over the days.
Individually developed features and functionality can eventually “give birth”
to a working product when integrated or assembled later on. <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
Each
individual feature or list item is known as a “Product Backlog Item” or a “user
story” in simple language. Therefore, the product backlog or the master list is
fundamentally composed of product backlog items or user stories. The user story
represents a product feature, and is individually developed by the team members
during the development process – the daily sprints. Each story can be minutely
defined. The description, acceptance criteria (Points which need to be
“fulfilled” or satisfied before which the story can be considered as
successfully developed), its importance in the project, and the manner in which
it is supposed to be integrated into the final product, etc. are mentioned for
each user story.<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
Once the
feature list is created, it is arranged depending upon the importance of each
user story in the product backlog. Important user stories are arranged in the
“top” portion of the list, lesser important stories in the middle, and the
least important features and functionality in the bottom portion. <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify; text-indent: -14.2pt;">
<!--[if !supportLists]--><b>4.<span style="font-weight: normal;">
</span></b><!--[endif]--><b>Sprint planning meeting – Planning how to develop the
product features<o:p></o:p></b></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
The
product backlog functions as the main “backbone” of all development related activities
in Scrum. Once it is “developed” by the product owner and the stakeholders, the
actual development activity can start. A special meeting known as a “Sprint
Planning” meeting is held to initiate the development activity. The meeting is
attended by the entire development team, in addition to the product owner “PO”
and the scrum master “SM”. <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
The
meeting is held in two parts. In the first part, the product owner selects some
of the most important user stories or product features from the top of the
product backlog, and transfers them to a temporary list known as a “Sprint
Backlog” for development purpose. During the meeting, the product owner takes
the opportunity to explain each user story in details to the team members – how
user stories should be ideally developed, and what activities the team should
carry out so that each story can be marked as successfully completed.<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
During
the second half of the meeting, the development team analyses the sprint
backlog and distributes each story to individual team members. In practise, the
team members unanimously decide as to who should take up which story depending
upon their development skills and experience levels. Simple and easily
developable items are given to less experienced or “fresher” while difficult,
or more complex stories are taken up for development by more experienced and
senior programmers or developers. <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify; text-indent: -14.2pt;">
<!--[if !supportLists]--><b>5.<span style="font-weight: normal;">
</span></b><!--[endif]--><b><a href="http://www.quickscrum.com/Kernel/frmSupport.aspx">The daily sprints</a> – Developing the product features<o:p></o:p></b></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
This is
the main area of activity in Scrum. The entire product is developed in “bits”
and “pieces” through the daily sprint cycles. A sprint cycle is nothing but a
collection of working or “development” days during which the team members
actually sit in front of a PC and develop the functionality or product features.
The sprint cycle is time boxed and should not extend its deadline. <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
Each item
included in the sprint backlog during the sprint planning meeting should be
developed while the sprint is currently underway. A brief meeting known as a
“Daily Scrum Meeting” is held for a maximum of 15 minutes each day before the
team members start with their work. The purpose of the meeting is to get an
idea regarding how much work has been completed by each member the day before,
and what each member proposes to do “today”. If a team member is facing any
issues or problems, it can be mentioned during the meeting, and the scrum
master will ensure that the issue is quickly resolved. <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
In Scrum,
the daily sprints can typically last from 2 weeks up to a maximum of one month.
The duration of the sprint is decided during the second stage - the project
release - and it should not be extended under any circumstances - even if any
of the user stories in the sprint backlog have not been developed, or whose
development is incomplete. <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify; text-indent: -14.2pt;">
<!--[if !supportLists]--><b>6.<span style="font-weight: normal;">
</span></b><!--[endif]--><b>Sprint review – Checking and verifying productivity
(Is the development OK?) <o:p></o:p></b></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
Scrum
emphasises upon the development of “shippable” functionality at the end of
daily sprint cycle. Each user story developed during the daily sprint is
checked by the product owner and verified for its reliability, acceptance
levels, and whether it is “bug free”. In Scrum, it is very important to deliver
error free features – each <b><a href="http://www.quickscrum.com/Kernel/frmFeature.aspx">user story</a></b> should be properly tested for any
regression, and whether it satisfies the acceptance criteria linked with its
development. <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
Just
after the daily sprint cycle ends, a meeting is immediately held to review the
development carried out by the team. It is important to differentiate between
the daily sprints and the sprint cycle. The daily sprint is the development
activity carried out by the entire team on one particular working day. Many
such “daily sprints” combine to form the “Daily Sprint Cycle”, also known as
the “product incremental cycle” in Agile. The meeting is held at the end of the
product incremental cycle – the daily sprint cycle. It is primarily attended by
the product owner, the scrum master, and the team members. It is not mandatory
for the stakeholders to attend this meeting. They can chose to attend it if
they so desire. <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
The main
objective of this event, or rather the meeting, is to check whether the
features have been developed by the team as per the production plan, and if the
functionality has any “manufacturing” defects. Each feature should be fully
tested for any flaws by the team before presenting it in this meeting. The product
owner verifies if the feature is error free and checks if it satisfies the
acceptance criteria linked with it. It is a kind of “final” check carried out
before presenting the development to the stakeholders and the project owners in
the subsequent sprint retrospective meeting. During the meeting, the product owner
instructs the team how it can improve its working and offer even better
productivity by employing more efficient programming practices and standards. <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpLast" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify; text-indent: -14.2pt;">
<!--[if !supportLists]--><b>7.<span style="font-weight: normal;">
</span></b><!--[endif]--><b>Sprint retrospective – Finalising product
functionality and contemplating about further improvement<o:p></o:p></b></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
Agile Scrum advocates client participation. The client
is a very important entity in Scrum, and has the final say as far as the
development of product features is concerned. The Agile manifesto primarily
stresses upon client participation and delivery of time bound product
increments because these two aspects are very important for developing
successful projects. A “satisfied” client often “comes back” to develop more
projects since successful projects help the client to earn higher profit
margins.<o:p></o:p></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
The retrospective provides an opportunity for the
entire team to demonstrate its productivity in front of the stakeholders and
clients. In addition to the product owner, scrum master, the development team,
the meeting may also be attended by end users, technical staff personnel,
vendors, distributors, and even other employees since the main purpose of the
meeting is to avail feedback from individuals and entities closely linked with
the market, and who have sound knowledge regarding what product features are
likely to “score” in the market once the product is launched, and what can aid
the product in “selling”. <o:p></o:p></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0.0001pt 14.2pt; text-align: justify;">
The retrospective also offers a chance for the entire
team as well as the client to reflect upon the development process, and discover
what more could be done to make the product better. Discussions are carried out
to ascertain the rate at which user stories are currently being developed by
the team, and what new processes or methods need to be introduced to quicken
the process.<span style="font-size: x-small;"><o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<b style="background-color: white; color: #333333; font-family: Arial, Tahoma, Helvetica, FreeSans, sans-serif; font-size: 15px; line-height: 20.790000915527344px;"><span lang="EN-US" style="background-attachment: initial; background-clip: initial; background-image: initial; background-origin: initial; background-position: initial; background-repeat: initial; background-size: initial; color: blue; font-family: Arial, sans-serif; font-size: 13.5pt;"><span style="color: #6699cc;"> <a href="http://www.quickscrum.com/Kernel/frmPricing.aspx?ENTITY=1" style="color: #6699cc; text-decoration: none;">Subscribe Free scrum tool from Quickscrum.com</a></span></span></b></div>
<script type="text/javascript"><!--
google_ad_client = "ca-pub-5127002032752269";
/* blog-1 */
google_ad_slot = "9377763837";
google_ad_width = 320;
google_ad_height = 50;
//-->
</script>
<script type="text/javascript"
src="//pagead2.googlesyndication.com/pagead/show_ads.js">
</script></div>Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-37416055368303614922014-07-21T21:32:00.000-07:002014-07-21T21:34:15.822-07:00Bharti soft tech pvt ltd, India announces to launch Quick scrum tool by 1st July 2014, it will be available to download from http://www.quickscrum.com.<div dir="ltr" style="text-align: left;" trbidi="on">
<iframe allowfullscreen="" frameborder="0" height="349" src="//e.issuu.com/embed.html#9602890/8686793" width="525"></iframe></div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-60889222052577938842014-07-21T06:40:00.001-07:002014-07-21T06:40:11.347-07:00Bharti soft tech pvt ltd, I... | MyPRGenie<a href="http://www.myprgenie.com/view-publication/bharti-soft-tech-pvt-ltd-india-announces-to-launch-quick-scrum-tool-by-1st-july-2014-it-will-be-available-to-download-from-http-www-quickscrum-com?user_type=mc&ref_no=NTk4Mzcz%250A#.U80YM8HAehY.blogger">Bharti soft tech pvt ltd, I... | MyPRGenie</a>Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-11069366738901313312014-07-21T00:48:00.002-07:002014-07-21T00:48:42.432-07:00What Should The Perfect And Ideal Daily Stand-Up Scrum Meeting Consist Of As Per The Official Scrum Guide?<div dir="ltr" style="text-align: left;" trbidi="on">
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify;">
<span lang="EN-US" style="font-size: 13.5pt;">The
daily stand-up<span class="apple-converted-space"> </span><b><a href="http://www.quickscrum.com/" target="_blank">scrum
meetings</a></b><span class="apple-converted-space"> </span>play a vital
role in ascertaining that the development activity is carried out in a
sustained manner. The meetings are usually time boxed to 5–15 minutes and are
held standing up to remind people to keep the meeting short and to-the-point.
Stand-up scrum meetings also help to find potential pitfalls experienced during
ongoing sprints. It is important to know how the daily meetings are carried
out, and what they should ideally consist of. On the basis of official scrum
guide specified by Jeff Sutherland and Ken Schwaber, the originators of<span class="apple-converted-space"> </span><b><a href="http://www.quickscrum.com/Kernel/frmFeature.aspx" target="_blank">scrum methodology</a></b>, the article
tries to explain in details about the daily scrum meetings.</span><span style="font-size: 13.5pt;"><o:p></o:p></span></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify;">
<br /></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify; text-indent: -14.4pt;">
<span lang="EN-US" style="font-family: Symbol; font-size: 13.5pt;">·</span><span color:black="" lang="EN-US" mso-ansi-language:en-us="" new="" roman="" serif="" style="font-family: "; font-size: 13.5pt;" times=""> <span class="apple-converted-space"> </span></span><b><span lang="EN-US" style="font-size: 13.5pt;">Who should attend
the meeting?</span></b><span style="font-size: 13.5pt;"><o:p></o:p></span></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify;">
<span lang="EN-US" style="font-size: 13.5pt;">Everyone
associated with the<span class="apple-converted-space"> </span><b><a href="http://www.quickscrum.com/Kernel/frmSupport.aspx" target="_blank">scrum project</a></b><span class="apple-converted-space"> </span>should attend the meeting. It is
important for the scrum master and the team members to remain present, while
the product owner and stakeholders too can remain present if they desire to do
so.</span><span style="font-size: 13.5pt;"><o:p></o:p></span></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify;">
<br /></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify; text-indent: -14.4pt;">
<span lang="EN-US" style="font-family: Symbol; font-size: 13.5pt;">·</span><span color:black="" lang="EN-US" mso-ansi-language:en-us="" new="" roman="" serif="" style="font-family: "; font-size: 13.5pt;" times=""> <span class="apple-converted-space"> </span></span><b><span lang="EN-US" style="font-size: 13.5pt;">What should be
discussed during the meeting?</span></b><span style="font-size: 13.5pt;"><o:p></o:p></span></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify;">
<span lang="EN-US" style="font-size: 13.5pt;">It is
very important to remain focused and only discus about those topics which are
directly related and associated with the sprint activity. The attendees should
try not to wander off the main topic and discus about other trivia which are
not pertaining to the scrum activity. In fact, the guide is specific about
discussing topics which are directly connected to the sprint to be carried out
during the particular day, even other topics dealing with the project, or
project related issues should be avoided during the stand-up meetings. There
are special provisions like the sprint retrospective meeting to discuss about
such issues.The main topics to be included during the meeting should consist of:</span><span style="font-size: 13.5pt;"><o:p></o:p></span></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify; text-indent: -14.4pt;">
<span lang="EN-US" style="font-size: 13.5pt;">- What
tasks were accomplished during the sprint carried out the day before?</span><span style="font-size: 13.5pt;"><o:p></o:p></span></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify; text-indent: -14.4pt;">
<span lang="EN-US" style="font-size: 13.5pt;">- Which
tasks are to be developed today?</span><span style="font-size: 13.5pt;"><o:p></o:p></span></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify; text-indent: -14.4pt;">
<span lang="EN-US" style="font-size: 13.5pt;">-
<span class="apple-converted-space"> </span>Did the particular
team member face any problems or impediments during the sprint implementation?
If so, what were they?</span><span style="font-size: 13.5pt;"><o:p></o:p></span></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify;">
<span lang="EN-US" style="font-size: 13.5pt;"> </span><span style="font-size: 13.5pt;"><o:p></o:p></span></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify; text-indent: -14.4pt;">
<span lang="EN-US" style="font-family: Symbol; font-size: 13.5pt;">·</span><span color:black="" lang="EN-US" mso-ansi-language:en-us="" new="" roman="" serif="" style="font-family: "; font-size: 13.5pt;" times=""> <span class="apple-converted-space"> </span></span><b><span lang="EN-US" style="font-size: 13.5pt;">In what order
should the discussions be carried out?</span></b><span style="font-size: 13.5pt;"><o:p></o:p></span></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify;">
<span lang="EN-US" style="font-size: 13.5pt;">There
is a lot of flexibility while deciding about the order in which the discussions
can be carried out during the meeting. Team members can take turns in discussing
about what they have achieved, and what they plan to do on the particular day.
Alternatively, the<span class="apple-converted-space"> </span><b><a href="http://www.quickscrum.com/" target="_blank">scrum
master</a></b><span class="apple-converted-space"> </span>may decide who
should speak first and which team member should follow the discussion. A
popular method is to take up discussions regarding important tasks first,
followed by the order of priority. The order of discussion can vary from
project to project, and from need to need. </span><span style="font-size: 13.5pt;"><o:p></o:p></span></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify;">
<br /></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify; text-indent: -14.4pt;">
<span lang="EN-US" style="font-family: Symbol; font-size: 13.5pt;">·</span><span color:black="" lang="EN-US" mso-ansi-language:en-us="" new="" roman="" serif="" style="font-family: "; font-size: 13.5pt;" times=""> <span class="apple-converted-space"> </span></span><b><span lang="EN-US" style="font-size: 13.5pt;">Where and when
should the meetings be held?</span></b><span style="font-size: 13.5pt;"><o:p></o:p></span></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify;">
<span lang="EN-US" style="font-size: 13.5pt;">The
stand up meetings should be ideally held at the place of work, and in front of
the task board. While they can be conducted almost everywhere, including
conference rooms, holding the meetings in the actual place of work can help the
team members to remain more focused and target oriented. The meetings should be
held before the daily sprint is initiated.</span><span style="font-size: 13.5pt;"><o:p></o:p></span></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify;">
<br /></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify; text-indent: -14.4pt;">
<span lang="EN-US" style="font-family: Symbol; font-size: 13.5pt;">·</span><span color:black="" lang="EN-US" mso-ansi-language:en-us="" new="" roman="" serif="" style="font-family: "; font-size: 13.5pt;" times=""> <span class="apple-converted-space"> </span></span><b><span lang="EN-US" style="font-size: 13.5pt;">How to sustain the
energy levels during the meetings?</span></b><span style="font-size: 13.5pt;"><o:p></o:p></span></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify;">
<span lang="EN-US" style="font-size: 13.5pt;">The
stand up meetings are also commonly referred to as “huddles” by many people,
simply because each team member stands very close to the next one during the
meeting. The scene is much similar to the scrum used in rugby. The proximity
often encourages the team members to become proactively involved in the
discussion. The energy levels start rising up as each team member briefly, and
professionally, discusses and outlines his or her activity for that particular
day. The meeting is to be held in such a manner that the “atmosphere” becomes
charged up with anticipation, and each member focuses upon the goals he or she
plans to achieve during the sprint carried out that day.</span><span style="font-size: 13.5pt;"><o:p></o:p></span></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify;">
<br /></div>
<u1:p></u1:p>
<u1:p></u1:p>
<u1:p></u1:p>
<u1:p></u1:p>
<u1:p></u1:p>
<u1:p></u1:p>
<u1:p></u1:p>
<u1:p></u1:p>
<u1:p></u1:p>
<u1:p></u1:p>
<u1:p></u1:p>
<u1:p></u1:p>
<u1:p></u1:p>
<u1:p></u1:p>
<u1:p></u1:p>
<br />
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify;">
<b><span lang="EN-US" style="background: white; color: blue; font-family: "Arial","sans-serif"; font-size: 13.5pt; mso-ansi-language: EN-US;">
<span style="color: #6699cc;"><a href="http://www.quickscrum.com/Kernel/frmPricing.aspx?ENTITY=1">Subscribe Free scrum tool from Quickscrum.com</a></span></span></b><span style="font-size: 13.5pt;"><o:p></o:p></span></div>
<div style="margin-bottom: .0001pt; margin: 0cm; text-align: justify;">
<b><span lang="EN-US" style="background: white; color: blue; font-family: "Arial","sans-serif"; font-size: 13.5pt; mso-ansi-language: EN-US;"><br /></span></b></div>
<script type="text/javascript"><!--
google_ad_client = "ca-pub-5127002032752269";
/* blog */
google_ad_slot = "7638835437";
google_ad_width = 728;
google_ad_height = 90;
//-->
</script>
<script src="//pagead2.googlesyndication.com/pagead/show_ads.js" type="text/javascript">
</script>
</div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-1572311573373503732014-07-14T02:36:00.001-07:002014-07-14T03:39:20.584-07:00What Is Sprint Planning And What Do The Sprint Planning Meetings Actually Consist Of Or Include?<div dir="ltr" style="text-align: left;" trbidi="on">
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<span lang="EN-US">The
primary objective of a <b><a href="http://www.quickscrum.com/Kernel/frmSupport.aspx">sprint planningmeeting</a> </b>is to discuss and plan about what the development team intends to
build or develop in the upcoming sprint, and how the individual members of the
team are prepared to go about with their development activity. Though most
experts refer it to as a “single” meeting, it is in fact segregated into two
unique parts. The first part concentrates upon what the team is actually asked
to build or develop, and is attended by the team members as well as the <b><a href="http://www.quickscrum.com/">product owner</a></b>. The second part of the
meeting focuses upon how the team members will proceed with the actual
development work. The team members are to mandatorily attend both the parts of
the meeting, while the product owner is committed to attending the first part
only. He or she can however attend the second part if he or she wishes to do
so. <o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<center>
<script type="text/javascript"><!--
google_ad_client = "ca-pub-5127002032752269";
/* quickscrum_sidebar-right-1_AdSense1_250x250_as */
google_ad_slot = "4063893831";
google_ad_width = 250;
google_ad_height = 250;
//-->
</script>
<script type="text/javascript"
src="//pagead2.googlesyndication.com/pagead/show_ads.js">
</script></center><br>
<b><span lang="EN-US">The first part of the sprint planning meeting<o:p></o:p></span></b></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<span lang="EN-US">During
the initial part of the meeting, the product owner has an opportunity to
explain in depth about the set of <b><a href="http://www.quickscrum.com/Kernel/frmFeature.aspx">user stories</a></b> to be developed during the sprint. It is a rapid-fire type of
discussion in which the product owner initially explains the user stories, and
subsequently the team members start asking questions regarding the points they
are not clear about. The product owner has many responsibilities and roles to
play. The person represents the client’s interests, explains how the stories
are to be linked up in the future, and keep tabs during the entire development
activity carried out by the team members. The objective of the meeting is to
provide enough information, or brief the team members regarding the development
activity required so that each member can carry out his or her part without any
confusions or problems. <o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<span lang="EN-US">The
questions typically asked during this stage of the meeting are: <o:p></o:p></span></div>
<div class="MsoListParagraphCxSpFirst" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify; text-indent: -14.4pt;">
<!--[if !supportLists]--><span lang="EN-US" style="font-family: Symbol;">·<span style="font-family: 'Times New Roman';"> </span></span><!--[endif]--><span lang="EN-US">What is the acceptance or “passing” criteria
of all the stories?<o:p></o:p></span></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify; text-indent: -14.4pt;">
<!--[if !supportLists]--><span lang="EN-US" style="font-family: Symbol;">·<span style="font-family: 'Times New Roman';"> </span></span><!--[endif]--><span lang="EN-US">What kind of data sources need to be used?
Where will the data originate from, and where will it go?<o:p></o:p></span></div>
<div class="MsoListParagraphCxSpLast" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify; text-indent: -14.4pt;">
<!--[if !supportLists]--><span lang="EN-US" style="font-family: Symbol;">·<span style="font-family: 'Times New Roman';"> </span></span><!--[endif]--><span lang="EN-US">How should the developed component look
like once it is fully developed?<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<b><span lang="EN-US">The second part of the sprint planning meeting<o:p></o:p></span></b></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<span lang="EN-US">During
the second part of the meeting, the team further analyses the user stories and
focuses upon creating the <b><a href="http://www.quickscrum.com/Kernel/frmFeature.aspx">sprint backlog</a></b>
which includes the user stories, or the set of requirements and functionality
to be developed by the team members during the sprint. The team typically
segregates the user stories into individual tasks, and links up, or associates each
task with a certain time scale i.e. the duration in which the particular task
is to be developed. Generally the tasks are planned to be completed on an
hourly basis, however, the time period can be more depending upon the
complexity and the levels of functionality to be incorporated into the given task.
Another main objective of this part of the meeting is to accept the user
stories as practical and “doable”, and to reject those stories which cannot be
catered to, owning to various reasons. <o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<span lang="EN-US">The
duration of the entire sprint planning meeting can range from two hours up to
eight hours depending upon the number of user stories involved, and the levels
of complexity. The rule of the thumb is to spend one hour of discussion for
each week of sprint. <o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<span lang="EN-US"><br /></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<span lang="EN-US"><b style="background-color: white; color: #333333; font-family: Arial, Tahoma, Helvetica, FreeSans, sans-serif; font-size: 15px; line-height: 20.790000915527344px; text-align: center;"><span style="color: blue;"> <a href="http://www.quickscrum.com/Kernel/frmPricing.aspx?ENTITY=1" style="color: #6699cc; text-decoration: none;">Subscribe Free scrum tool from Quickscrum.com</a></span></b></span></div>
<br />
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
</div>Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-89561340558159886502014-07-10T06:07:00.000-07:002016-07-13T04:05:01.607-07:00What to Consider Before Writing User Stories in Scrum So They Can Be More Effective and Meaningful<div dir="ltr" style="text-align: left;" trbidi="on">
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<b><span lang="EN-US">User stories in scrum<span style="font-size: small;"><o:p></o:p></span></span></b></div>
<br />
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify; text-indent: 7.2pt;">
<span lang="EN-US">A user story is the main functional unit in <a href="http://www.quickscrum.com/" target="_blank"><b>scrum methodology</b></a>. When any project is
taken up for development using scrum, the specific requirements for that
particular project is stated by creating a set or development requirements,
which are termed as <b>user stories</b> in
scrum. Usually the <a href="https://www.quickscrum.com/ScrumTool" target="_blank"><b>product owner</b></a>
creates the <b>product backlog </b>– the
list of requirements needed to develop the project. The product backlog items
are referred to as user stories by scrum professionals. Once the product
requirement list is created, a small set of the requirements (user stories) are
transferred to the sprint backlog during the sprint planning meeting for development
purposes. The stories are explained to the team members in the first half of
the sprint planning meeting. During the second half, team members distribute
the stories after breaking them down into development tasks. A sprint backlog
is prepared in this way. Subsequently, the team starts developing the
functionalities of the user stories during the daily sprint. In scrum, the
entire project is governed on the basis of the user stories.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify; text-indent: 7.2pt;">
<span lang="EN-US"><br /></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify; text-indent: 7.2pt;">
<span lang="EN-US">The official scrum guide does not attempt to provide a
specific definition that can describe the “structure” of a particular user
story. The guide actually explains what a user story is, and what part it is
supposed to play in the project. It fails to provide a standard format which
can explain as to how a user story should really look like. Maybe, the reason
why the guide fails to provide a structural definition is because development requirements
can vary from one particular project to another. So, it becomes difficult to standardize a specific
format compatible to all types of projects.
The guide, however, states that the user story should ideally be composed
of three constituent parts, or include there main aspects:<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpFirst" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify; text-indent: -14.4pt;">
<!--[if !supportLists]--><span lang="EN-US">1.
</span><!--[endif]--><span lang="EN-US">A
written description or a graphical representation of the entity which forms a part
of the project<o:p></o:p></span></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify; text-indent: -14.4pt;">
<!--[if !supportLists]--><span lang="EN-US">2.
</span><!--[endif]--><span lang="EN-US">A detailed
conversation, or an explanation which additionally describes the functionality
in greater details<o:p></o:p></span></div>
<div class="MsoListParagraphCxSpLast" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify; text-indent: -14.4pt;">
<!--[if !supportLists]--><span lang="EN-US">3.
</span><!--[endif]--><span lang="EN-US">The
acceptance criteria or “Done” meaning which specifies what the entity should
include, how it should function, and the particular manner how it should migrate
or integrate into the project<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<b><span lang="EN-US">What should be considered while writing or
creating user stories<o:p></o:p></span></b></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<span lang="EN-US">While
writing the user stories, certain points are important, and should be adhered
to for the user stories to be effective and developmental:<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpFirst" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify; text-indent: -14.4pt;">
<!--[if !supportLists]--><span lang="EN-US" style="font-family: "symbol";">·<span style="font-family: "times new roman";"> </span></span><!--[endif]--><b><span lang="EN-US">Stakeholders
should create or write the user stories<o:p></o:p></span></b></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify;">
<span lang="EN-US">The
investors and the stakeholders are funding the project for financial gains.
Each project has a financial value attached to it in terms of how much the
project will be worth in the market. The stakeholders know which user stories
are important, and which functionalities will increase the value of the
project. Therefore, they are the ideal individuals to define and create the
list of requirements or the user stories. The product owner carries out the
work on their behalf, and represents their interests while the project is being
implemented.<o:p></o:p></span></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify; text-indent: -14.4pt;">
<!--[if !supportLists]--><span lang="EN-US" style="font-family: "symbol";">·<span style="font-family: "times new roman";"> </span></span><!--[endif]--><b><span lang="EN-US">Using
simple tools to represent user stories<o:p></o:p></span></b></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify;">
<span lang="EN-US">In
the manual system, stories are written down on index or story cards specially
designed for scrum. The scrum index cards are very convenient to work with, and
are generally pinned on the scrum board while the sprint is underway. It is
important to use a tool that is small in size, so it can be easily stored and
pinned on the scrum board. It should be easily readable, simple to understand,
and effective. The more simple and effective the tool is, the easier it would
be for the team to understand and use it. <o:p></o:p></span></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify; text-indent: -14.4pt;">
<!--[if !supportLists]--><span lang="EN-US" style="font-family: "symbol";">·<span style="font-family: "times new roman";"> </span></span><!--[endif]--><b><span lang="EN-US">Time
to be allotted to the user story<o:p></o:p></span></b></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify;">
<span lang="EN-US">Scrum
advocates time bound activities. Each activity in scrum has a certain duration
associated with it, and is “time boxed”. It is important not to exceed the time
limit to get the most out of scrum. Each user story is allotted a certain
duration within which its development should be completed. It is essential that
each user story is completed in the time allotted to it since it has a certain
importance value (story points) attached to it. The project turns out to be
cost effective only when the right duration of time is allotted to each user
story, and each story is completed in the time allotted to it. If the time
limit is not allotted, the project becomes expensive and its ROI decreases.</span></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify;">
<span lang="EN-US"><br /></span></div>
<div class="MsoListParagraphCxSpFirst" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify; text-indent: -14.4pt;">
<!--[if !supportLists]--><span lang="EN-US" style="font-family: "symbol";">·<span style="font-family: "times new roman";"> </span></span><!--[endif]--><b><span lang="EN-US">Describing
and stating important non-functional aspects<o:p></o:p></span></b></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify;">
<span lang="EN-US">Certain
user stories need to be explained in further details so the team members can
properly understand them. The user stories may be very important in terms of
how they provide a solution for a particular end-user related requirement. They
may or may not be technically complex, but it may be important for the team
members to know what part the user stories are likely to play, and how much
important they are as far as the overall project development is concerned. Such
non-technical aspects of user stories should be explained properly so a better
overview and understanding of the project related requirements is availed. <o:p></o:p></span></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify; text-indent: -14.4pt;">
<!--[if !supportLists]--><span lang="EN-US" style="font-family: "symbol";">·<span style="font-family: "times new roman";"> </span></span><!--[endif]--><b><span lang="EN-US">Fixing
the story priority<o:p></o:p></span></b></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify;">
<span lang="EN-US">Each
user story has a certain level of importance attached to it development. It is
important to prioritize the user stories, so the correct time can be fixed for
its development. Important user stories, or those which have more importance
attached to their development, should be assigned a higher priority, and
sufficient time should be allotted for completing them. On the other hand, less
important stories ought to be assigned less time and priority because they do
not carry much financial value with regards the functionality they offer. . <span style="font-size: x-small;"><o:p></o:p></span></span></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify;">
<span lang="EN-US"><br /></span></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: center;">
<a href="https://www.quickscrum.com/ScrumTool" target="_blank"><span lang="EN-US"><b><span style="color: blue;">Subscribe Free scrum tool </span></b></span></a></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify;">
<span lang="EN-US" style="font-size: 10.0pt;">
</span></div>
<div class="MsoListParagraphCxSpLast" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify;">
<span lang="EN-US" style="font-size: 10pt;"><br /></span></div>
<div class="MsoListParagraphCxSpMiddle" style="margin: 0cm 0cm 0.0001pt 14.4pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify; text-indent: 7.2pt;">
<span lang="EN-US" style="font-size: 10.0pt;"><br /></span></div>
</div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0tag:blogger.com,1999:blog-651611792114842420.post-71384816223137679622014-06-23T01:08:00.000-07:002014-06-23T01:08:58.119-07:00Does Agile Exist Once You Implement It In Your Project?<div dir="ltr" style="text-align: left;" trbidi="on">
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
As on today, if you
search for Agile, or Agile related information over the internet, you will be
greeted with search result pages displaying all sorts of information pertaining
to Agile – right from Agile training and coaching to Agile gurus offering their
“esteemed” insights and experience relating to various Agile frameworks. More
recently, it has become very common to see scaled versions of Agile appearing
in the searches – SAFe, Scaled Agile, ScrumButs, AgileLive, Jira Agile, <a href="http://www.quickscrum.com/"><b>Quickscrum</b></a> - the
list is not big but worthy of being considered – and all of them proclaiming
their efficiency in being “effective”, and above all “Agile”. It would be
wonderful to know more about these versions, but a basic question always keeps
on popping up – Is the client really following Agile in a true sense? Are you a
hard-core Agile supporter or a ScrumBut? Maybe, it would be more worthwhile to
ascertain whether you, or your client, are in fact following Agile in the first
place, let alone other scaled versions of Agile. <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
Here are a couple of
pointers to help you know if you are “Agile” or not.<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<b>Is development carried out through iterations?<o:p></o:p></b></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
Needless to say, the
main purpose of implementing an <a href="http://www.quickscrum.com/Kernel/frmPartner.aspx"><b>Agile framework</b></a> is to benefit through product
increments in a consistent manner. Nobody can claim they’re following Agile if
their project development process does not support regular product increments
at the end of sprints. In addition to iterative development, Agile
implementation should also support dynamic collaboration – sharing of feedback
and information amongst the product owner, scrum master, scrum team, and the
stakeholders. Iterative development and collaborative nature are Agile trademarks,
and it is most essential for organisations to support these features if they
claim to be Agile. <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<b>Can changes be incorporated during the product
development cycle?<o:p></o:p></b></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
One of the main
reasons why people opt for Agile is its ability to incorporate changes in the
product definition even while the product development process is currently
underway. It is a unique selling feature of all Agile frameworks, and is
synonymous with developing a project while still maintaining its business value
– at all times. Irrespective of the changes taking place in the market –
whether big or small – the project development process should have, and retain,
its capability to dynamically change the functionality developed, and offered,
by the product features as and when necessary. Agile projects should support
this feature.<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<b>Can development be carried out in “bits and pieces”
rather than “as a whole”?<o:p></o:p></b></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
Perhaps what makes
Agile frameworks so unique are their iterative structures supporting daily
sprints. In scrum or XP, the product development is carried out in the form of
daily sprints. Special events are held to plan the sprint (<a href="http://www.quickscrum.com/Kernel/frmSupport.aspx">the sprint planningmeeting</a>) and ensure that proper and acceptable product increments are availed
at the end of sprints (sprint reviews and retrospectives). The development
carried out in “bits and pieces” should result into shippable functionality
(<a href="http://www.quickscrum.com/Kernel/frmFeature.aspx">successfully developed user stories</a>), and should also be acceptable to the
project owners (stakeholders). “Small sized” consistent development, which is
bug free, should have the capability to later integrate in a correct functional
manner so as to form the “complete” product – an euphemism which conveys
“Development in pieces to be later integrated to form the actual product.”<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
As on today,
organisations are not just limited to using traditional versions of Agile
frameworks. There are subtle variants, which can be scaled up or down as per
the need, and which can be “tailored” to meet the unique project development
needs of business concerns. It may not be possible to state or define the exact
set of parameters which a project management methodology, or framework, should
satisfy to be considered Agile, since Agile is all about “inspecting” and
“adapting”. The main essence of Agile lies in its ability to change itself, its
working, and mould itself to suit the specific development related needs, as
the case may be. <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<br />
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
However, it may be
certainly possible to “check” for some “trademark” features to ascertain
whether Agile exists in a project or not.<span style="font-size: x-small;"><o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<span style="color: red;">Use Free scrum tool from <b><a href="http://www.quickscrum.com/">www.quickscrum.com</a></b></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt; text-align: justify;">
<b>Source:- </b></div>
<table border="0" cellpadding="0" cellspacing="0" style="border-collapse: collapse; width: 408px;"><tbody>
<tr height="20" style="height: 15.0pt;">
<td height="20" style="height: 15.0pt; width: 306pt;" width="408"><a href="http://ezinearticles.com/8576627">http://EzineArticles.com/8576627</a></td></tr>
</tbody></table>
</div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0Paris, France48.856614 2.352221900000017748.6894645 2.0294984000000178 49.0237635 2.6749454000000177tag:blogger.com,1999:blog-651611792114842420.post-24062191458681846322014-06-20T02:31:00.001-07:002014-06-20T02:31:55.852-07:00Quickscrum - Tool to Consider<div dir="ltr" style="text-align: left;" trbidi="on">
<div style="background: white; line-height: 18.0pt; margin-bottom: .0001pt; margin: 0cm; text-align: justify; vertical-align: baseline;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="border: 1pt none windowtext; color: #666666; padding: 0cm;">This tool for managing projects
scrum type, to manage in a simple way the entire project, ie customer, product
owner, members, assignments, sprints, priorities, task description, and even
even graphs showing progress and evolution .</span><span style="color: #666666;"><o:p></o:p></span></span></div>
<div style="background: white; line-height: 18.0pt; margin-bottom: .0001pt; margin: 0cm; text-align: justify; vertical-align: baseline;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="border: 1pt none windowtext; color: #666666; padding: 0cm;">It's kind of collaborative,
allowing dragging of objects, as is done for example in<span class="apple-converted-space"> </span></span><strong><span style="border: 1pt none windowtext; font-family: inherit, serif; padding: 0cm;">Trello</span></strong><span class="apple-converted-space"><span style="border: 1pt none windowtext; color: #666666; padding: 0cm;"> </span></span><span style="border: 1pt none windowtext; color: #666666; padding: 0cm;">,
app that we use and we are very pleased also.</span><span style="color: #666666;"><o:p></o:p></span></span></div>
<div style="background: white; line-height: 18.0pt; margin-bottom: .0001pt; margin: 0cm; text-align: justify; vertical-align: baseline;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="border: 1pt none windowtext; color: #666666; padding: 0cm;">It can be used in free mode, up
to 5 users, 3 projects but without any ability to store files, while offering
other alternatives (fee-and not so expensive) that increase performance, of
course.<span class="apple-converted-space"> </span>Right?</span><span style="color: #666666;"><o:p></o:p></span></span></div>
<div style="background: white; line-height: 18.0pt; margin-bottom: .0001pt; margin: 0cm; text-align: justify; vertical-align: baseline;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="border: 1pt none windowtext; color: #666666; padding: 0cm;">Say to prove it is worth it
because it really is very easy and convenient to use.</span><span style="color: #666666;"><o:p></o:p></span></span></div>
<div style="background: white; line-height: 18.0pt; margin-bottom: .0001pt; margin: 0cm; text-align: justify; vertical-align: baseline;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="border: 1pt none windowtext; padding: 0cm;"><span style="color: #666666;">To access the official site, I
leave the link: </span><span class="apple-converted-space"><span style="color: red;"> </span></span></span><strong><span style="border: 1pt none windowtext; padding: 0cm; text-decoration: none;"><a href="http://www.quickscrum.com/"><span style="color: red;">http://www.quickscrum.com</span></a></span></strong><span style="color: #666666;"><o:p></o:p></span></span></div>
<div style="background: white; line-height: 18.0pt; margin-bottom: .0001pt; margin: 0cm; text-align: justify; vertical-align: baseline;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="border: 1pt none windowtext; color: #666666; padding: 0cm;">If someone was using it, would
be nice to tell us what your opinion on this software is because it's like
everything else, as you will be entering information and interacting with the
app, you are giving certain situations to solve.</span><span style="color: #666666;"><o:p></o:p></span></span></div>
<div style="background: white; line-height: 18.0pt; margin-bottom: .0001pt; margin: 0cm; text-align: justify; vertical-align: baseline;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="border: 1pt none windowtext; color: #666666; padding: 0cm;">One thing I asked was if the
development team can connect to applications like: Test link, Mantis or
Redmine, and I responded that for the next release plan to incorporate a bug
tracking.</span><span style="color: #666666;"><o:p></o:p></span></span></div>
<br />
<div style="background: white; line-height: 18.0pt; margin-bottom: .0001pt; margin: 0cm; text-align: justify; vertical-align: baseline;">
<span style="border: 1pt none windowtext; color: #666666; padding: 0cm;"><span style="font-family: Arial, Helvetica, sans-serif;">It will be a matter of
following your steps and see how this another module that also serves both us
us.</span><o:p></o:p></span></div>
</div>
Mrugesh Panchalhttp://www.blogger.com/profile/11297069547561653310noreply@blogger.com0