The core of agile software development according to Scrum is regularly releasing product increments to the customer. The software’s functions are gradually extended, but the customer receives a version of their software right after the first sprint. That’s why at the end of each sprint, a review meeting is held where the development team presents the new functions to the customer. In this article, we will explain why it makes sense for the customer to participate in the reviews and why they should test the software created for them intensively and at an early stage.
Introduction to the possibilities of Git and Stash We met Jens Schumacher (Group Product Manger Dev Tools) during our last visit to Atlassian …
We are often contacted by customers with very rough, technical requirements lists for software projects. In cases like this, the first project step for //SEIBERT/MEDIA is to turn the customer’s requirements list into a product backlog that highlights how the customer benefits from the requirements. This is not a trivial task and requires time and resources. But why should the customer pay for this preparation work that has nothing to do with actually completing the project?
An enterprise Wiki is not only a new technology for many employees (at least within the company environment); it also requires a change in the normal communication- and collaboration patterns throughout the entire company. Through our experiences with dozens of company Wiki projects, we know that the successful introduction of a Wiki usually depends upon three factors: technology; organization; and culture. This article – the first of three articles on this topic – is dedicated to the challenges of technology.
Many companies are unsure of how a successful Wiki project should be started and executed. This article will give you an overview and inform you of the basics. //SEIBERT/MEDIA/ offers transparent services. Ultimately, as the saying goes, we’re also just cooking with water, but we’ve collected many experiences regarding the process for Wiki-projects, which we will happily explain here – regardless of whether or not you are currently running a project with us, are planning a project with us, or simply wish to be more successful with your Wiki – without our help.
Stash 3.2 offers you a few helpful updates. Branch compare already allows you to view differences between two branches and with Stash 3.2 you can now create a pull request with one click. You will know the code changes, that will be merged, before you create the pull request. Click to read about all the updates.
Within software development there are distributed version control systems, with especially git currently most popular. More and more teams are recognizing the advantages of DVCS and migrate from central version management. The market offers numerous products which enable teams of developers to manage their git repositories. All have their advantages. The most mature and most feature rich solution for an enterprise is in our opinion Atlassian’s Git repository management system Stash. We have collected 99 reasons, which all are argue for Stash and show why it is reasonable to test Stash, regardless whether a transition to Stash in the planning or has been started. 99 reasons – none longer than a Twitter tweet.